Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+Cut\s+numbers\s*$/: 85 ]

Total 85 documents matching your query.

41. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: "Paul J. Piercey" <p.piercey@nl.rogers.com>
Date: Sun, 18 Mar 2007 09:38:14 -0000
Hi Chris, I wouldn't think so. A callsign is a callsign and is part of your identity and thusly required by law; in Canada anyway. A signal report or contest exchange is not something that is legally
/archives//html/CQ-Contest/2007-03/msg00281.html (8,684 bytes)

42. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: Claude Du Berger <duberger.miousse81@globetrotter.net>
Date: Sun, 18 Mar 2007 07:39:34 -0400
Is it considered acceptable to use cut numbers in a callsign when CQing in a contest? For instance, I use G8D, so could I use GUD, or for GU8D could I use GUUD? Chris G3SJJ __________________________
/archives//html/CQ-Contest/2007-03/msg00282.html (7,760 bytes)

43. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: Zack Widup <w9sz@prairienet.org>
Date: Sun, 18 Mar 2007 09:06:17 -0500 (CDT)
I wouldn't reconnemd it. For one thing, in some calls how do you know where the number goes? Suppose you heard "UENN". Is that UE9N or U5NN? 73, Zack WNSZ ____________________________________________
/archives//html/CQ-Contest/2007-03/msg00285.html (7,299 bytes)

44. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: Mirko S57AD <miroslav.sibilja@amis.net>
Date: Sun, 18 Mar 2007 15:35:54 +0100
Cut numbers were introduced decades ago to cut a bit longish numerical (ciphererd) radiogrammes and were supposed to use just in strictly numerical textes. Thhey should never be used in mixed (both l
/archives//html/CQ-Contest/2007-03/msg00286.html (9,930 bytes)

45. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: Bill Turner <dezrat@copper.net>
Date: Sun, 18 Mar 2007 07:56:01 -0700
ORIGINAL MESSAGE: -- REPLY FOLLOWS -- I suspect the rules in the UK are the same as the US: You are required to transmit your callsign. GUUD is not it. Bill W6WRT ____________________________________
/archives//html/CQ-Contest/2007-03/msg00288.html (7,775 bytes)

46. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: G3SJJ <g3sjj@btinternet.com>
Date: Sun, 18 Mar 2007 14:57:26 +0000
Thanks for all the comments. 1 - I would never, ever, ever use cut numbers in a callsign for whatever reason. 2 - I raised the subject because I was listening to a contest station over the weekend wh
/archives//html/CQ-Contest/2007-03/msg00289.html (7,657 bytes)

47. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: "Eric Hilding" <dx35@hilding.com>
Date: Sun, 18 Mar 2007 18:42:32 -0800
How on earth did you get "U" as a cut number for "8"? I'm completely Baffled. 73... Rick, K6VVA _______________________________________________ CQ-Contest mailing list CQ-Contest@contesting.com http:
/archives//html/CQ-Contest/2007-03/msg00302.html (7,541 bytes)

48. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: "Leigh S. Jones, KR6X" <kr6x@kr6x.com>
Date: Sun, 18 Mar 2007 19:09:16 -0700
Cut numbers are problematic; there are conflicting cut numbers systems with resulting ambiguities. Perhaps the most commonly accepted cut numbers system merely eliminates all extra dashes beyond the
/archives//html/CQ-Contest/2007-03/msg00304.html (9,955 bytes)

49. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: G3SJJ <g3sjj@btinternet.com>
Date: Mon, 19 Mar 2007 07:37:00 +0000
Yes, Eric. I messed up and that also. The post was bad humour on my part. I had heard a station giving what I thought was a cut-number in a callsign and wanted to draw attention to it. I would never
/archives//html/CQ-Contest/2007-03/msg00306.html (8,584 bytes)

50. [CQ-Contest] Cut Numbers (score: 1)
Author: "Martin Monsalvo, LU5DX" <lu5dx@yahoo.com>
Date: Tue, 20 Mar 2007 12:16:49 -0700 (PDT)
Tree, N6TR recently wrote: "...Sometimes people complain about me sending "73" when I am finishing a QSL in the SS - but aside from this being a nice thing to say to someone, it acts as a "mini CQ" -
/archives//html/CQ-Contest/2007-03/msg00351.html (8,936 bytes)

51. [CQ-Contest] Cut numbers (score: 1)
Author: "Mike Fatchett" <mike@mallardcove.com>
Date: Mon, 28 May 2007 20:37:05 -0600
As a mediocre cw guy I have to say that cut numbers threw me almost every time. I get in number rhythms and ..-- followed by ._ _. _ just killed me. The letter O for zero threw me too. I am sure thos
/archives//html/CQ-Contest/2007-05/msg00294.html (7,399 bytes)

52. Re: [CQ-Contest] Cut numbers (score: 1)
Author: Steve Harrison <k0xp@dandy.net>
Date: Tue, 29 May 2007 04:07:13 +0000
When your rate is 3 or 4 per MINUTE, then yes, it surely can; it can bump you up another Q per minute. I have no doubt that at least some Europeans experienced such rates, if only briefly, during the
/archives//html/CQ-Contest/2007-05/msg00302.html (10,287 bytes)

53. Re: [CQ-Contest] Cut numbers (score: 1)
Author: "Marijan Miletic', S56A" <s56a@bit.si>
Date: Tue, 29 May 2007 09:48:36 +0200
I went to two guitars concert last night in order to reset my brain from 36 hours torture of QRN and single breaking CW tone! Once I went to movie "Amadeus" after 48 hours of CQ WW CW and almost ende
/archives//html/CQ-Contest/2007-05/msg00307.html (7,589 bytes)

54. [CQ-Contest] Cut Numbers (score: 1)
Author: "James Cassidy" <jimki7y@earthlink.net>
Date: Tue, 29 May 2007 21:52:21 -0700
While it may be time saving to send cut numbers, is there any advantage if the receiving op need repeats to get it right. I think one normal transmission would be quicker than repeating. I recall a M
/archives//html/CQ-Contest/2007-05/msg00330.html (7,788 bytes)

55. Re: [CQ-Contest] Cut numbers (score: 1)
Author: DL8MBS <prickler.schneider@t-online.de>
Date: Wed, 30 May 2007 07:25:28 +0200
Steve Harrison schrieb: In this years ARRL CW I received a report including "enn" - and trying to answer in the same language I replied "tu enn 7e" as I chose my power as 75 Watts - he requested a re
/archives//html/CQ-Contest/2007-05/msg00331.html (8,060 bytes)

56. Re: [CQ-Contest] Cut numbers (score: 1)
Author: Steve Harrison <k0xp@dandy.net>
Date: Wed, 30 May 2007 06:05:36 +0000
The problem here was that the other operator just didn't anticipate, and thus expect, cut numbers in the actual power level. Cut numbers are 99% OK when it comes to the signal report; but when it com
/archives//html/CQ-Contest/2007-05/msg00332.html (9,707 bytes)

57. Re: [CQ-Contest] Cut numbers (score: 1)
Author: John Geiger <n5ten@yahoo.com>
Date: Wed, 30 May 2007 07:02:36 -0700 (PDT)
It seems that for NA ops, limited use of cut numbers works well. Using a T for leading zeros seems to work pretty well, and using O for a middle zero in the serial number does ok most of the time. Us
/archives//html/CQ-Contest/2007-05/msg00353.html (8,903 bytes)

58. Re: [CQ-Contest] Cut numbers (score: 1)
Author: "Rex Maner" <k7qq@netzero.net>
Date: Wed, 30 May 2007 14:05:45 -0000
Quack Says, I consider myself a fair to medium CW operator and find that Cut Numbers in the 5nn are OK but ENN would throw me totally out of sync. I also can deal with T 91 but don't give me T9A, and
/archives//html/CQ-Contest/2007-05/msg00355.html (11,707 bytes)

59. Re: [CQ-Contest] Cut Numbers (score: 1)
Author: Steve Harrison <k0xp@dandy.net>
Date: Wed, 30 May 2007 15:07:36 +0000
My point was that a skilled op, upon being called by someone, can often make an impromptu estimate whether that other station can handle being sent cut numbers. For example, when called by someone of
/archives//html/CQ-Contest/2007-05/msg00358.html (10,893 bytes)

60. Re: [CQ-Contest] Cut numbers (score: 1)
Author: "Sean D. Fleming (K8KHZ / Dr. Wouff Hong)" <k8khz@yahoo.com>
Date: Sun, 3 Jun 2007 22:42:58 -0400 (Eastern Daylight Time)
As I am following the the thread I have figured out why someone was sending me A for a 1 the other night. I thought or thought for a long time That people were sending A's instead of 1's but I though
/archives//html/CQ-Contest/2007-06/msg00064.html (7,365 bytes)

Current List: 41 - 60
Page: [1] [2] [3] [4] [5]
This search system is powered by Namazu