| Date | User | User score | Status | Toot summary & link |
|---|
| 2025-02-05 20:37:01 | df5go@radiosocial.de | 23 | Success! | Today, I participated in the 2m segment of the Winter Fieldday / Bayerischer Bergtag from my usual VHF hill which is also valid for POTA (#DE0315).In two hours I made 15 contacts to German and Czech stations using my trusty FT-818 (6 W out) and a 4 element yagi.With today's activity I accomplished three #HamChallenge|s at once:• #HC06S (Contest)• #HC29S (xOTA activation)• #HC38S (Morse contact)#hamradio #amateurradio #amateurfunk #contest @hamchallenge |
| 2025-03-14 10:46:53 | dd1mat@mastodon.social | 17 | Success! | The BCC spring QSO party was a nice opportunity to meet many of the fellow BCC members. Thanks @DJ5CW for 80M #cw contact. Regarding the #hamchallenge, time to tick off the challenges HC06S, HC30S, HC33S and HC38S |
| 2025-05-20 19:34:25 | yo3gnd@mastodon.radio | 31 | Success! | @hamchallenge The condx were terrible and I really, really hoped for a 6m qso, but nothing happened. I did hear F4JRC, about 2000 km away, on the magic band #HC28S.
Contacting other xOTA stations wasn't as easy as the usual P2P or P2S, but I did get ~15 in the log, not counting multiple parks and multiple ops setups. #HC16S
I even had some CW qsos with other hams with whom I share this instance #HC38S, but I couldn't find someone for #HC30 #hamchallenge |
| 2025-08-30 03:02:13 | davekuk@mastodon.radio | 13 | Success! | #HC38S Made CW Contact during POTA QSO |
| 2025-09-16 13:59:11 | mcdanlj@social.makerforums.info | 16 | Success! | Since the week in the US is considered to start on Sunday, my 10 CW POTA QSOs on Sunday definitely count as #HC38S within the week.At the beginning of this year, I had not finished learning all the morse symbols. Now ¾ of my QSOs have been CW, I hunt POTA at 20WPM, run POTA at 15WPM, and am progressing towards my goal of conversational CW at 20WPM by the end of the calendar year. (I may or may not succeed, but it's nice to have a goal!) |
| 2025-09-19 21:24:09 | ei7ijb@mastodon.radio | 9 | Working on it... | For the 38th challenge, 'Make a contact on Morse code!’, I will make a contact using Morse Code one day. #hamchallenge HC38 @hamchallenge |
| 2025-09-21 18:22:35 | bgarfoot@kind.social | 21 | Success! | Thanks to FL Digi, I think there's a semblance of a POTA CW contact in there. 599 both ways. While I'm going to count HC38S, I think I'm going to leave morse code to those who actually fully understand what they're doing (for now).Thanks to K4ZGB for putting up with whatever I sent out. |
| 2025-09-21 18:23:35 | bgarfoot@kind.social | 21 | Success! | Thanks to FL Digi, I think there's a semblance of a POTA CW contact in there. 599 both ways. While I'm going to count HC38S, I think I'm going to leave morse code to those who actually fully understand what they're doing (for now).Thanks to K4ZGB for putting up with whatever I sent out.#amatuerRadio #hamradio |
| 2025-09-21 22:54:03 | df5go@radiosocial.de | 23 | Success! | This week I did two #POTA activations. The majority of contacts were in #CW, so also #HamChallenge #HC38S completed.#hamradio #amateurradio #amateurfunk |
| 2025-09-23 11:19:34 | DL6PL@social.darc.de | 9 | Success! | Had a really nice standard #cw QSO with YL3AD as YU/DL6PL on 17 m last week. It was my first QSO with Latvia, so I was very happy, that he offered a QSL card via bureau. #hamchallenge #HC38S @hamchallenge |
| 2025-09-29 09:40:20 | dd1mat@mastodon.social | 17 | Success! | 52 Week Ham Radio Challenge 2025 - Week 38: Make a contact on Morse code!In my 20 years of ham radio, I have always missed FP St.Pierre & Miquelon. Therefore I built a vertical and managed to work FP5KE on a few bands in #CW I had a monoband vertical earlier but now focused on multi-band possibilities through feeding with a wiremann twinline.#hamchallenge HC38S HC33S |
| 2025-10-13 14:54:05 | siwli@toot.berlin | 20 | Success! | And yesterday, I completed another @hamchallenge:I made my very first contact in morse code. It was over a very short distance and we agreed on the contents of the QSO beforehand, but I managed to understand what @df5go sent and successfully sent my own callsign and report. So HC38S#hamchallenge |