Rugby League Scoreboard: Tackle Count, Clock and Every Scorebug Overlay Explained
A rugby league scoreboard must show the score, a count-up match clock and the tackle count from one to six. The tackle count is what makes the sport legible: it tells you whether the next play is an attacking option or a kick. It is also the reason a rugby league bug cannot be a rugby union bug with the point values changed.
A rugby league scoreboard graphic needs four things on screen at all times: the score, the match clock, the tackle count and possession. That graphic is also called the scorebug; both words describe the same thing. Almost every element on one is either a score or a clock. Rugby league adds a third kind: a possession state that changes several times a minute, is derived from neither of the others, and is read more often than the score. Get it wrong and the graphic is useless even if the score is perfect. This page is part of the master scoreboard guide.
What a rugby league scoreboard must show
| Element | Why it matters | Source of data |
|---|---|---|
| Tackle count, 1 to 6 | The primary read. On the sixth tackle the attacking side kicks or loses the ball. | Operator or official feed |
| Possession indicator | The tackle count means nothing without knowing whose set it is. | Possession state |
| Score | Try 4, conversion 2, penalty goal 2, drop goal 1. Four increments, not one. | Scoring events |
| Match clock | Counts up through two forty-minute halves and runs through nearly everything. | Timekeeper, via feed or operator |
| Sin bin countdown | A second clock counting down while the match clock counts up. | Sin bin events |
| Player-count pill | Twelve against thirteen changes how you read every set that follows. | Sin bins and send-offs |
| Team codes, colours and branding | Readable at broadcast size, plus the sponsor position that funds the production. | Team and competition records |
The tackle count is the bug
The attacking side gets six tackles. On the sixth it usually kicks, because the seventh hands the ball over. Every read a viewer makes runs through that number, which is why the tackle count should be at least as prominent as the score, and often larger. Most rugby scoreboard templates get this backwards, because they were designed for sports where the score is the only thing that changes.
What makes it hard to build is that it is derived from nothing else on the bug. The clock does not predict it, the score does not affect it, and it changes on an event that is neither a stoppage nor a score. It resets on a possession change, a penalty, a scrum, and on a set restart, the call known in the NRL as six again, where the count returns to one without play stopping at all. A bug that only resets at obvious breaks in play will be wrong for the whole of the following set.
Three consequences follow:
- It is the highest-frequency element on the bug, so it is where latency becomes visible. A score arriving a second late is invisible. A tackle count one behind reads as a broken graphic, and a frozen one is the most conspicuous failure available in the sport.
- It must move with the possession indicator, not near it. If the count resets to one while the chevron still points at the other team, the bug is contradicting itself on screen. The reset and the flip are one state change, not two.
- The sixth tackle is a state, not a pop-up. It deserves a colour change and a last-tackle label on the count module itself. A full lower third at the moment of the most decisive kick in the set is the wrong graphic at the wrong time.
The display form is a genuine design choice with no settled answer. A six-dot progress track shows at a glance how much of the set is left. A single large numeral survives being scaled down for mobile and vertical outputs, which is where a growing share of lower-tier rugby league is watched. Either works. What does not work is a small tackle count tucked beside the clock.
The clock: continuous, until it is not
Rugby league runs two halves of forty minutes and the clock counts up through almost everything: play the balls, scrums, tries, conversions, kick-offs. This is the opposite problem to Australian rules, where the clock stops constantly. Here the naive implementation is right most of the time, which is worse, because it fails only when people are paying attention.
The exceptions are the ones that matter. The clock stops for injuries, and in most competitions for a video referee or Bunker review, which is precisely when drift gets noticed. It also has to be clamped: it should never roll past 40:00 in the first half or 80:00 in the second without an explicit extra-time state behind it. And the siren is not the end of play, since the period runs on until the ball next becomes dead, so the graphic has to sit at its ceiling without looking broken while play continues.
Golden point extra time is sudden death: the next score of any kind wins, including a one-point drop goal. Competitions differ on what happens if nobody scores, some declaring a draw at the end of the extra period and others playing on, so that has to be a competition setting rather than an assumption in the graphic. The same goes for point values, which are not universal constants: a try is four points in league and five in union.
Then there is the second clock. A sin bin countdown runs down from 10:00 while the match clock runs up, so a rugby league bug can be showing two clocks moving in opposite directions at once, with up to two active per team. Whether the countdown pauses during stoppages is a competition rule, not a design preference. Both clocks need tabular, fixed-width digits so nothing shuffles sideways as the numbers change.
Scoring events and what the bug does
Rugby league has four scoring increments, and the graphic should make the size of each obvious before the viewer reads the number:
- Try, four points. The full celebration: scorer, team, minute, career tries on a milestone. Intercept tries and penalty tries are worth labelling separately.
- Conversion, two points. Follows the try within a couple of minutes, so the two graphics have to queue cleanly rather than fight each other. A missed conversion still needs its own treatment, because the score does not move and viewers will check.
- Penalty goal, two points. Same value as a conversion, different event, and it should not reuse the conversion graphic.
- Drop goal, one point. Usually a late-game decision, and the graphic that most often has to appear while the tackle count is at five or six.
The Bunker changes the sequencing. When a try goes to the video referee, hold the score, suppress the flash, and show a review banner until the decision comes back. Only then does the score move. If the graphic celebrates first and corrects afterwards, an overturn forces it to subtract four points on air, which viewers read as a fault in the stream rather than a decision by the officials.
Cards, sin bins and player counts
A yellow card in rugby league means ten minutes in the sin bin, long enough to decide a match, so a persistent countdown and a player-count pill are not optional extras. A red card is a send-off for the rest of the match.
The two need to be visibly different states, not the same pill in another colour, because one expires and the other does not. A yellow-outlined countdown that clears itself at 0:00 tells a different story from a red-outlined permanent marker. They also stack: a side can be down to eleven with one player due back and one gone for good. Sides run thirteen on the field with four on the bench, so the reference point for the pill is always thirteen.
Head injury assessments sit alongside the disciplinary graphics but should not look like them. An HIA is not a sanction, it holds until the player is cleared or ruled out, and the tone should stay factual.
Extensions: the stats worth putting on the bug
A scorebug extension is a stat panel that pops out of the bug, on a milestone in auto-mode or on demand from the operator. For rugby league, the ones that earn the space:
- Possession and territory split. Two bars, each summing to a hundred. Worth holding back until around the ten-minute mark, because a percentage taken from two sets of six is noise dressed up as insight.
- Try-scorer leaderboard. Two columns, updated when a try is confirmed rather than when it is scored.
- Kicker record. Conversions from attempts and the success rate, with penalty goals counted separately, since they are a different kick from a different place.
- Head-to-head comparison. Runs, run metres and tackles made, scaled to the larger of the two values so the bars stay honest.
- Squad graphic. Thirteen starters with the four-man bench below, captain marked.
Extensions can carry a sponsor position, which is often what turns a graphics package from a cost into revenue.
How LIGR drives a rugby league scoreboard
The hard part below the top tier is not the design, it is the data. No official feed exists for most rugby league played anywhere in the world, and the tackle count in particular sits in no external database. LIGR takes an official feed where one exists and uses the LiveScore app where one does not. The operator presses the buttons for real events, tackle, possession change, try, conversion, sin bin, and the graphics update from them. Every press is timestamped, which is what makes the stat extensions and automated highlights possible from the same input. Below the elite level, the scoring app is the feed.
LIGR's rugby scoreboard is data-bound in Fuse, so the tackle count is a variable rather than a redraw, and so are the score, clock, possession state and any active sin bin countdown. Graphics are designed in Rive and render in HTML5, so a new competition or sponsor is a theme change, not a rebuild, and there is no graphics machine at the ground.
Game Plans handles the automation: pre-match sequences, event-triggered graphics, break playlists and live playlists. The Control Room gives an operator manual control of the same graphics where a producer wants a human in the loop, and auto-mode runs the package with no operator at all. The same platform delivers 640 or more DAZN National League football matches a season, which is the volume test for automation of this kind: see the DAZN National League project.
LIGR is the official graphics provider to Queensland Rugby League. More on the rugby page.
Frequently asked questions
What is a rugby league scoreboard overlay?
A rugby league scoreboard overlay is the graphic layered over a live video feed that carries the match state: score, match clock, possession and the tackle count from one to six. The same graphic is also called a scorebug. In rugby league it must add a sin bin countdown and a player-count marker when either applies, because a rugby scoreboard without a tackle count leaves the viewer unable to read the set.
What does a rugby league scorebug need to show?
The score, the match clock, the tackle count from one to six, and which team is in possession. Add a sin bin countdown and a player-count indicator whenever either is active, plus team codes with colours and competition branding. Possession and territory percentages, try scorers and kicking records belong in pop-out extensions rather than on the bug itself.
Why is the tackle count on the scorebug?
Because the attacking side has six tackles to score before handing the ball over, so the tackle number is what tells a viewer whether to expect an attacking play or a kick. It changes several times a minute, far more often than the score, which makes it the most-read element on the bug and the one most obviously wrong when a graphic falls behind.
Does the rugby league clock stop?
Rarely. The clock counts up through two forty-minute halves and runs through play the balls, scrums, tries and conversions. It is stopped for injuries, and in most competitions for a video referee or Bunker review. That makes a naive clock right most of the time and wrong exactly when the audience is watching a stoppage closely.
How should golden point be shown on the scorebug?
With an explicit extra-time state, because the rules change rather than continue. Golden point is sudden death: the next score of any kind wins, including a one-point drop goal. Competitions differ on what happens if nobody scores, some declaring a draw and others playing on, so the format should be a competition setting rather than an assumption baked into the graphic.
How long is a rugby league sin bin and how is it displayed?
A yellow card is ten minutes off the field. The bug shows a countdown from 10:00 attached to that team, running down while the match clock runs up, plus a player-count pill showing the side is a player short. Up to two can be active per team, and whether the countdown pauses during stoppages is a competition rule.
Can you run rugby league graphics without an official data feed?
Yes, and for most rugby league you have to, because no feed exists and the tackle count is not held in any external database. LIGR uses an official feed where one exists and its LiveScore app where one does not. An operator logs tackles, possession changes, scores and cards as they happen, and the graphics update from those events.
Rugby league scoreboard graphics without a graphics truck
Cloud-native overlays, no hardware at the ground, one operator or none.