DX News Bulletins: How to Follow DXpeditions Before They Start

A DX cluster tells you what is on the air right now, and that is exactly why it is not enough on its own. By the time a rare station appears as a spot, you have no time to prepare, no time to check the antenna and no time to decide which band and mode deserve your attention. DX news bulletins work in the opposite direction. They tell you about operations days or weeks before they start, and they tell you how the team plans to operate, which is often more useful than the callsign itself. This guide explains the main kinds of source, what each is good at, how to read an announcement, and how to turn a stream of news into a short list of contacts that you actually try to make.

Why Bulletins Still Matter in the Age of Spots

Spots are a snapshot. A bulletin is a plan. If you know that a team will be on a remote island next month, that they carry two stations, and that they intend to focus on 40 and 30 metres at night, you can decide in advance what to prepare. You might raise a receiving antenna, clear a weekend, update your log with the entity that you need, or simply check the propagation path on a calendar of solar conditions. Without the bulletin you are reacting. With it you are choosing.

Bulletins also help you avoid the common mistakes. Operators often chase a callsign that is not new for them because they did not know which entity it counts for, or they miss the first days of an operation because they assumed that it began later. News gives the dates in UTC, the name of the entity and the way to confirm a contact afterwards. Our article on how to work a DXpedition describes the second half of this process, which is what to do when the station is on the air.

The Main Kinds of DX News Source

There are several families of source, and a sensible station follows one or two of each. None is perfect, but together they give a good picture of what is coming.

• Weekly bulletins by email. Several long-running newsletters collect announcements, QSL information and operating plans into one message every week. The Daily DX is a well-known example, and the OPDX Bulletin and the 425 DX News are others. Each has its own style, its own editors and its own network of contributors.
• Calendars of announced operations. The NG3K Announced DX Operations page lists operations by date, with the callsign, the location and links to the team website. It is the quickest way to see what is planned for the next few weeks.
• Team websites and social posts. The best source for an individual operation is the team itself. Its page usually has the schedule, the equipment, the QSL manager, the online request form and the live log.
• Logging and spotting services. Club-level and personal alert tools notify you when a wanted station is spotted, which complements the planning that a bulletin gives you.
• Club and national society news. Local reports on a national DX group or society page often include announcements that are of special interest in your region.

Most operators find that one weekly bulletin, one calendar and the website of each team that they care about is enough. More than that and the volume becomes tiring, and you start to skip the news altogether.

How a Typical Announcement Is Structured

Announcements follow a loose pattern. Learn it once and you can read any of them in a few seconds. The first line gives the callsign and the place, usually followed by the entity name in capitals, because the entity is what matters for DXCC. The next lines give the dates and the operators, then the bands, modes and the number of stations, and finally the QSL route and the link to the page of the team.

The dates deserve attention. They are almost always in UTC and they are almost always approximate for the end of the operation. Weather, transport and licence problems move arrival and departure by a day or two. A good habit is to put the start date in your calendar and to treat the end date as the earliest possible finish, so that you do not leave the chase until the last evening.

Also read what is not said. A listing that names no operators, no website and no QSL manager is often an early rumour and not a confirmed plan. A listing that includes a licensing note, a boat or aircraft booking and a team page is much more likely to happen.

Comparing Types of Source

The table below summarises what each kind of source is best for, so you can decide where to spend your attention.

The sources complement each other. The bulletin and the calendar tell you what to expect, the team website tells you how the operation develops, and spots and alerts tell you the moment to sit down at the radio.

Turning News Into a Plan

Information is only useful if it changes what you do. A short routine makes this easy.

1. Compare with your own list. Check each announced entity against your log. Our guide to how DXCC works explains the entity list and how to track what you need. Ignore what you already have confirmed on the bands that you use.
2. Rank by difficulty. A rare entity with two stations is a priority. A common entity with a large team is something you will work almost by accident.
3. Check the path. Look at the distance and direction from your location, and think about which hours should be open. A simple great circle map helps to see whether the path crosses the pole or the auroral zone.
4. Mark the calendar. Note the first possible day and the expected focus of the team, such as low bands or digital modes.
5. Prepare the alert. Add the callsign to your cluster filter or your alert tool, as described in our article about automating DX spot alerts.

With five minutes of work per announcement, you end up with a short list of targets for the month and not a long list of vague intentions.

Different Goals, Different Reading

A new DXCC chaser wants entities. A contester wants activity in a specific contest, with multipliers. A low band enthusiast wants to know who plans to be on 160 and 80 metres. A satellite operator wants rare grids. Read the same bulletin with your own goal in mind and you will find that most items are irrelevant and a few are essential. That is how you keep the volume manageable.

Reading Between the Lines

The wording of an announcement contains hints that experienced chasers learn to notice. Phrases such as “if the permit arrives” or “weather permitting” mean that the plan is conditional. A statement that the team will be active “on all bands” is not the same as one that lists the bands and the number of stations, because the second shows real equipment. A team with a record of earlier operations, a donated-funds statement and a clear schedule is more reliable than a first-time announcement with a short text.

Look also at the QSL information. A team that describes its logging system, the upload frequency and the online request process has thought about the end of the operation as well as the beginning. That makes it more likely that your contact will be confirmed with little effort.

When news conflicts, trust the team itself over any third-party report. A bulletin edits and forwards information, which means a delay and sometimes an error, while the team page is the primary source. If two bulletins disagree about the dates, check the team page and wait for an update before you change your plans.

Avoiding Rumours and Spam

Not every announcement is real. Some are optimistic plans that never get a licence, and a few are deliberate hoaxes. Four simple checks reduce the risk.

• Look for a primary source. A team page, a society announcement or a licensing authority note is better than a repost.
• Check the callsign format. The prefix must belong to the claimed entity, as our guide to callsign prefixes explains.
• Wait for confirmation of spots. If a callsign appears only in one spot and nobody can hear it, do not call endlessly.
• Be careful with QSL requests. Use the route that the team publishes on its own page, and do not send money to an address that you saw only in a comment.

Treat the quiet period before an operation as normal. Many teams publish little until they arrive on site, and that does not mean that the plan has been cancelled.

During the Operation

When the operation starts, switch from planning to action. Watch the team page for notes about schedule changes, because teams often switch bands according to propagation and post a short update. Use the live log search if the team provides one, to check whether you are already in the log on a given band before you call again. Do not ask for personal reports on the team page or social media; the operators are busy and the log will be uploaded after the end of the operation. Finally, remember that thanks and brief positive reports are welcome and that long chat or complaints about the operating style are not.

Keeping the Routine Light

The danger with any news habit is that it grows until it becomes a chore. Set a fixed time once a week, for example on the evening that your bulletin arrives, and spend ten minutes on it. Read the announcements, copy the interesting dates into your calendar and add the new callsigns to your alert list. Then close the message. Between those sessions, look at the news only when an operation that you care about is under way. This keeps the hobby enjoyable, and it ensures that your radio time is spent on contacts and not on reading. If you chase several awards, keep one simple text file with the entity, the dates and the notes, and delete each line when the operation ends.

Common Mistakes

• Following too many sources. You skim, miss the key item and stop reading.
• Treating end dates as fixed. Operations often end earlier or later than announced.
• Ignoring the time zone. The dates and times are UTC, which can shift the local day.
• Waiting for the spot. A planned approach lets you be ready on the first day, when pileups are smallest.
• Forgetting confirmation. Check how the team handles QSLs before the operation ends, as our guide to Club Log and OQRS shows.

The Bottom Line

DX news bulletins turn the cluster from a surprise machine into a planning tool. Pick one weekly bulletin, one calendar of announced operations and the team pages of the entities you need, compare them with your own list, and put the start dates in your diary. Read each announcement for the entity, the dates in UTC, the bands and the confirmation route, and check the team page whenever sources disagree. A few minutes a week is enough to make sure that the next rare station is a planned contact and not a missed one.

Frequently Asked Questions

What is a DX news bulletin?

It is a regular message, usually weekly, that collects announcements about DX operations, QSL information and other news for radio amateurs who chase distant stations.

Are DX news bulletins free?

Some are free and some are offered by subscription or with limited free access. Check each publisher’s own page for current terms before you decide which to follow.

How far ahead are operations announced?

Large expeditions are often announced months in advance, while smaller operations may appear only a few days before. The calendar pages are updated as new plans arrive.

Should I use bulletins or the DX cluster?

Use both. Bulletins and calendars give notice of what will happen, and the cluster shows what is happening now. Together they cover planning and action.

What time zone do bulletins use?

Almost all use UTC for dates and times. Convert them to your local time when you put them in a calendar.

How do I know an announcement is genuine?

Look for a team website, named operators, licensing information and a QSL route. When in doubt, wait for confirmation on the team’s own page.