开云体育

Thanks to all who participated in RG#9. Nearly everyone who did has submitted their logged code groups. If any more logs are submitted I'll update the results. You can check the "final" results at the

RG#9 is today, Fri 2/23, from 21:00 - 23:00 UTC. This is a 2-hour sprint limited to only 25 code groups per TX list. Please see the event description: /g/RG/message/188 Good luck! 73,

Following is the RG schedule through April, for events #9 through #13. These will be 2-hour events, two per month with alternating day and time: *2nd Tuesdays @ 15:00 - 17:00 UTC* *4th Fridays? @

*Roster & Results for RG Event Nr. 9* Feb 23rd @ 21:00 -23:00 UTC (2 hours) There is a limit of 25 code groups per operator for this event (= 50 TX points max). Please see event details *HERE* (

Welcome to RandomGram Event Nr. 9 *Roster & Results.* The current roster of participants, team assignments, and updated results when available, are posted *HERE (

An awful lot of behind the scenes February data gathering, QSL and station status work on Drew's table. Go for it Drew.... LOL Randy

Hi Vern, Yes, going to have a short event later this month, TBA soon. 73, Drew/AF2Z

Drew? Rested up enough from K3Y to think about a February RandomGram #9? A short 2 - 3 hour event might be easy for all. -- NJ8L 13613S Vern

The current time didn’t work for me in Central (UTC-6)..Maybe an 8 hour event with ops limited to any 2 hours? -- 73 David VE4DL

Please don't consider a later timeframe if you'd like participation outside of North America. CWops gets around the timezone issue by running the CWT in four 1 hour slots, 13z 19z 03z and 07z. 73

Hi Jim, Unfortunately, there are many who will find a 2-hour sprint to be at an inconvenient time, no matter when. That is the disadvantage compared to a longer event. Here are two possibilities: -

Drew,I like a 2-hour window with to RandomGram codes.Because of the limited timeframe everyone wasexchanging information at a nice pace.The problem I experienced was the time 2300-0100.This translates

I will also chime in that I liked the 2-hour sprint format.? I think with only 10 groups, most folks peetered out towards the end, as they had sent their groups multiple times. Perhaps 20 groups is a

I also found the short RG 8 along with a week day time frame preferable. If you want to make it more challenging, add a larger TX list but just 10 was good enough for me. As others have mentioned,

I haven’t had a chance to participate because it’s during my commute home. Will Shattuck KN6TZK

Thanks for all the comments. A number of them were in favor of the short event and having a larger number of groups (on the TX List). I'll be kicking around a few ideas for doing this in the new year,

I also liked the 2-hour format and having it on a weekday evening. Plus, having the limited RG set and 2-hour window meant we were all encouraged to send our groups more than once if possible, so as

RG8 certainly seemed busier than all the previous events. I had a great time with lots of stations to work and mini pile-ups when I called CQ. Come on Drew, let's make this format permanent! John

I agree!? The shorter events concentrated the activity into a smaller space, making for more activity, more stations to hear and work.? I was also happy to see the event on a Tuesday rather than

Sri I missed it again.Will try harder next time 73