CQ-Contest
[Top] [All Lists]

[CQ-Contest] Announcing the half hour RTTY NS (NCCC Sprint) contest this

To: NCCC Main Reflector <nccc@groups.io>, NCCC-blue <nccc-blue@groups.io>, CQ-Contest Reflector <cq-contest@contesting.com>, "Reflector: Rtty" <rtty@groups.io>, "groups.io" <rttydigital@groups.io>
Subject: [CQ-Contest] Announcing the half hour RTTY NS (NCCC Sprint) contest this Thursday evening Western Hemisphere time.
From: Ed Radlo via CQ-Contest <cq-contest@contesting.com>
Reply-to: Ed Radlo <eddrad@aol.com>
Date: Tue, 5 Dec 2023 04:42:47 +0000 (UTC)
List-post: <mailto:cq-contest@contesting.com>
RYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRYRY

 

To all RTTY opsworldwide:  

This is a reminder thatonce again, the Northern California Contest Club is 
pleased to present our regular weekly half hourRTTY Sprint, aka the NS RTTY (or 
RTTY NS if you prefer), this Thursday evening WesternHemisphere time.  
Non-Western Hemispherestations are welcome in this contest as well.

The start time of the NCCCRTTY Sprint is always 0145Z, regardless of whether 
we’re on Standard Time orDaylight Savings Time. 

Last week, we had someregulars plus N6XB, Tom from Washington. Let’s have a big 
turnout this Thursday!

For those of you who arenew to our weekly NS RTTY’s, we use a variation of the 
NCJ Sprint’s QSY rule– 1 KHz QSY’s rather than 5 KHz – and allow same band 
duplicate contacts aftermaking at least one intervening contact.  If you need a 
fullexplanation of these special rules, send me an e-mail, and I’ll give you 
allthe details, e.g., a precise definition of our QSY rule. 

Remember to QSY afteryou’ve made a contact that you’ve solicited, and that both 
callsigns, yourname, your state, and your contact number are required as part 
of the exchangethat you send.  But don’t send a signalreport or other 
extraneous information.

After the contest, logsare not required to be submitted anywhere, but please 
remember to submit yourscore to www.3830scores.com.  It’s easy – on 3830, the 
name of thiscontest is “NCCC RTTY Sprint”.  Reporting your score, whether it 
bebig or small, helps build enthusiasm for this event. That in turn 
increasesparticipation for future editions, which benefits all of us. 

For those of you usingthe popular N1MM+ logger, the contest module to use is 
NSRTTYDUPE.  A goodset of example function keys is in the N1MM+ website's 
function key gallery,available for free download. 

Remember to try 15meters at the beginning of this Thursday night's contest – 15 
has been openwith spotlight propagation at 0145Z lately.

The details of ournext NS RTTY: 

Friday, 8 December2023 UTC, 0145Z to 0215Z (Thursday, 7 December 2023 in the 
Western Hemisphere)

--1745 to 1815 PST

--2045 to 2115 EST

-- (others in betweenthose two time intervals)

-- 160 meters: Try 1804, 1805, or 1806 during the last two minutes

-- 80/40/20/15meters:  mostly +83 kHz to +89 kHz up from the lower band edge

-- Same banddupes are allowed for credit after one intervening QSO

-- 1 kHz QSYrule, otherwise standard NCJ Sprint QSY rules

-- Multipliers arecounted anew on each band, so if 4 or 5 bands are open, 
you’ll get a lot ofmults!

-- 100W output powerlimit

Please visit https://www.ncccsprint.com/rttyns.html for complete rules and 
links to otherinfo. If you find any problems with the Web pages, please let me 
know so we canget them fixed. 

If you would like toreceive all the latest info about NS (both CW and RTTY), as 
well as a have avehicle for expressing your comments and questions, sign up for 
the NS mailinglist:  https://groups.io/g/nccc-blue. ;

Contestonlinescore.com has a slot set up for us if you’d like to make sure 
yourlogger is talking to the world.  Select “NCCC NA RTTY Sprint”. 

Report scores to 3830scores.com, and join us at 0300Z on 3610 kHz (+/- a 
fewdepending upon who else is on) for comments and questions. 

73, 

EdRadlo  AJ6V

eddrad@aol.com

 

_._,_._,_

 

 

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>