Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[VHFcontesting\]\s+\[222Activity\]\s+Anybody\s+for\s+222\.222\s+at\s+2222\s+UTC\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[VHFcontesting\]\s+\[222Activity\]\s+Anybody\s+for\s+222\.222\s+at\s+2222\s+UTC\?\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [VHFcontesting] [222Activity] Anybody for 222.222 at 2222 UTC? (score: 1): Author: David Olean <k1whs@metrocast.net>; Date: Tue, 22 Feb 2022 17:41:57 -0500; Alright! I knew this would be big. Almost as good would be 02:22 UT although it is actually on the 23rd, but I won't complain if anyone does it. I expect a report! Dave K1WHS Paul N1BUG -=-=-=-=-=-; /archives//html/VHFcontesting/2022-02/msg00022.html (8,524 bytes)
2. Re: [VHFcontesting] [222Activity] Anybody for 222.222 at 2222 UTC? (score: 1): Author: N1BUG <paul@n1bug.com>; Date: Tue, 22 Feb 2022 19:24:27 -0500; No one stepped forward for my proposed 2222Z QSO. Around 2300Z it started raining. By 0000Z when people showed up for Activity Night I had 25 degrees, HEAVY rain and already nearly 0.2" of radial ice; /archives//html/VHFcontesting/2022-02/msg00023.html (7,844 bytes)

Current List: 1 - 2
Page: [1]