Contest Calendar

Amateur radio contests — all 260 computed from sponsors’ own published rules

iCal feed/API

LRAL · LV

LRAL 4 May 80m Contest

Latvia's 80m contest on 4 May: four half-hour CW/SSB rounds and then two FT8 rounds, with Latvian districts as the multiplier.

Rules at lral.lvThe rules are the sponsor's. This page holds the dates and the facts.

When it runs

May 4, every year

  • 0700 → 0859session 1
  • 0915 → 1014session 2

Times are the sponsor's own clock in Europe/Riga, so the UTC instant moves an hour across a daylight-saving boundary. The runnings below are the resolved instants.

2 sessions run off the one anchor day; each is a separate running with its own log.

Next runnings

  1. → · 1h 59m2027

    in 214 days

    Logs due

  2. → · 59m2027

    in 214 days

    Logs due

  3. → · 1h 59m2028

    in 580 days

    Logs due

  4. → · 59m2028

    in 580 days

    Logs due

  5. → · 1h 59m2029

    in 945 days

    Logs due

  6. → · 59m2029

    in 945 days

    Logs due

Operating

Modes
CW / SSB / FT8/FT4
Bands
80m

CW 3515-3580 kHz; SSB 3605-3650 kHz; FT8 3577 kHz.

Exchange
A serial number and the two-letter Latvian or Riga district code (001 LM). RST may be sent but is not part of the number. The FT8 rounds use signal report and a four-character locator instead.
Power categories
All entrants 100 W
Logs
Cabrillo · due 14 days after the end
Who can enter
Entry limited to YL. K stations may be worked but cannot submit an entry.

'Dalibnieki: Visi Latvijas radioamatieri' -- all Latvian radio amateurs. The nolikums names no other entrants.

Where this comes from

Checked against the sponsor
Yes. The rule on this page was read off LRAL's own published rules. Link last confirmed 2026-08-19.
What the source says
lral.lv/hf-80m-nolikums/, the Latvijas Radioamatieru liga's own nolikums, which covers both events. 'Sacensibas notiek 6 turos / 18. novembri no 08.00-11.14 pec vietejа laika' with rounds 08.00-08.29, 08.30-08.59, 09.00-09.29 and 09.30-09.59 CW/SSB and 10.15-10.44, 10.45-11.14 FT8; '4. maija no 07.00-10.14 pec vietejа laika' with rounds 07.00-07.29, 07.30-07.59, 08.00-08.29 and 08.30-08.59 CW/SSB and 09.15-09.44, 09.45-10.14 FT8. ('pec vieteja laika' = local time.) 'Frekvences un tehniskie noteikumi: CW - 3515-3580 kHz; SSB - 3605-3650 kHz; FT8 - 3577 kHz. Raiditaju izejas jauda: <=100 W.' 'Dalibnieki: Visi Latvijas radioamatieri.' (Participants: all Latvian radio amateurs.) Exchange: 'Kontroles numurs CW un SSB turos ir QSO kartas numurs un divi burti, kas apzime Latvijas vai Rigas pilsetas radioamatieru rajonu (piemeram, 001 LM). RST var raidit, bet tas kontroles numura neietilpst' -- the serial and district only; RST may be sent but is not part of the number. The FT8 rounds carry no serials. Each QSO is one point; the multiplier is districts per round, or locator squares in the FT8 rounds. Classes: A (CW+SSB), B (CW), B1 (CW with a straight key), C (SSB), D (FT8), E (multi-op). 'Atskaites iesniedz 14 dienu laika pec sacensibam, sutot uz adresi: yltest@lral.lv.'
Recorded caveats
SPONSOR-ANCHORED LOCAL TIME. LRAL states the schedule 'pec vieteja laika' -- in local time -- and never in UTC, so the record carries timezone Europe/Riga and wall_clock times. The two blocks are encoded as sessions because LRAL puts a gap between them and says the FT8 rounds are a separate contest: 'FT8 tures ir atseviskas sacensibas, dalibnieki, kas starte FT8 darba veida, var startet ari kada no A, B, vai C klasem.' Both sessions carry the record's whole mode list, which the catalog cannot narrow per session; the split is stated here and in bands_note. One nolikums covers both dates, so both records cite the same URL.

Something wrong? How to report it — a link to the sponsor's own page is all it takes.

Take it with you

Add to Google CalendarSubscribe (iCal)This record as JSON

Add to Google Calendar puts the next running in as a single event. It is one event, not a subscription — come back for the one after it, or use the feed below.

Subscribe (iCal) carries this contest's runnings for the next twelve months as UTC instants and keeps them current. Apple Calendar, Outlook and Thunderbird take this address directly. Its identifiers are stable across deploys, so re-subscribing does not duplicate anything: https://contestclock.com/api/ics?id=lral-4-may-80m

Google has no working one-click subscribe. Paste that address into Settings → Add calendar → From URL. Google then polls it on its own schedule, often 8–24 hours, and that cannot be forced — so use Add to Google Calendar above if you want the next running in your calendar now.