Handball Scoreboard Graphics: Every Clock State and Suspension Clock a Scorebug Must Show
A handball scoreboard graphic must show the score, a count-up match clock, the period, and a live two-minute countdown for every suspended player, up to three per team at once. In a live broadcast the same graphic is also called the scorebug. The match clock keeps running while those players sit out, so the bug carries several independent countdowns against a clock that almost never pauses. No fixed-layout template can hold that.
What a handball scoreboard must show
Handball is a 60-minute, high-scoring sport with a temporary-suspension system built into its disciplinary code, so the persistent bug carries more live state than football or basketball does.
| Element | Why it matters | Source of data |
|---|---|---|
| Score (home : away) | Games routinely pass 25 goals a side, so the cell must hold two digits without the layout shifting | Scoring app or official feed |
| Match clock, counting up | Runs 0:00 to 30:00, then 30:00 to 60:00. The second half continues the count, it does not reset | Official timekeeper, mirrored in the scoring app |
| Period pill | 1st half, 2nd half, ET1, ET2, shootout. Drives which clock rules apply | Match state |
| Active suspension clocks | One tile per suspended player, jersey number and time remaining, up to three per team at once | Disciplinary event plus match clock |
| Player-count chip | 6v7 or 5v7 tells the viewer instantly why one team suddenly has space | Derived from active suspensions and red cards |
| Timeout pips | Three per match, maximum two in either half. Pips are the only way a viewer reads that budget | Timeout events |
| Team identity | Crest, abbreviation and primary colour, always visible | Competition and team records |
| Passive play indicator | Once the referee raises a hand, the attacking team has limited passes before the turnover | Referee signal, entered by the operator |
| Last 30 seconds chip | Endings are frantic and the disciplinary rules tighten. Frames the last half-minute of a period | Derived from the match clock |
| Shootout tracker | Replaces the clock entirely once a knockout tie goes to shootout | Shootout attempt events |
The clock is the hard part
Most handball scoreboard problems come down to one sentence: the suspension clocks are not the match clock, but they are measured in match time.
A two-minute suspension is two minutes of playing time, not wall-clock time. If the referees stop the clock for an injury or a team timeout, the suspended player's countdown stops with it. A bug that runs those timers off the browser's own clock drifts a few seconds every stoppage and is visibly wrong by the time the player returns. Every countdown has to be derived from the same match time the score is.
The other timing details that catch people out:
- The clock counts up and does not reset at half time. The second half runs 30:00 to 60:00. A template built for football, where each half restarts its count, shows 12:41 when the official clock says 42:41.
- Extra time restarts at 0:00. Two five-minute periods with a short break between. Because the displayed clock resets, suspension countdowns cannot be worked out from the number on screen. They carry their own remaining time.
- Suspensions cascade. When one countdown expires and another offence is already sanctioned, the next starts in the slot the first vacated. The bug needs an ordered queue, not three fixed boxes.
- Three tiles have to fit. Three concurrent suspensions per team is rare but legal, and the layout has to survive it without the tiles colliding with the score.
- Digits must be tabular. A proportional typeface makes the whole clock jump sideways when 9 becomes 10, or when the seconds tick from 0:09 to 0:08. Tabular figures keep every glyph the same width, so the clock sits still.
Rule of thumb: if you pause the match clock and the suspension countdowns keep running, the scoreboard is wrong. Every timer on a handball bug is a view of the same underlying match time.
Scoring events and what the bug does
Handball scoring is frequent and play restarts within seconds, so goal graphics have to be short, consistent and never in the way of the next attack.
- Goal. Score increments, scorer name and optional assist. The subtype matters editorially: open play, fast break, seven-metre throw or break-through. A fast-break goal is a different story to a set-piece goal.
- Own goal. The correct team's score increments, the graphic stays muted, and the player's goal tally must not move.
- Seven-metre awarded. A badge naming the fouling player, the benefiting team and the goalkeeper facing it. No score change yet.
- Seven-metre scored. Goal treatment with the seven-metre attribution attached, because seven-metre efficiency is tracked all match.
- Seven-metre missed or saved. A save credits the goalkeeper, a miss does not, and the two should never share an icon.
- Shootout attempt. Each updates a per-team rail of ticks and crosses before the graphic leaves screen.
The pattern holds across every sport we have documented: a scoring event is a number change plus an attribution plus a qualifier, and the qualifier is what makes the stat panels possible later.
Cards, suspensions and player counts
This is what separates a handball scoreboard from a generic one. Handball has a graded sanction ladder and most of it lives on the bug rather than in a one-off pop-up.
| Sanction | Effect on play | What the bug shows |
|---|---|---|
| Yellow card | Warning only. The player stays on | Short card overlay that must not spawn a suspension clock. A team is limited to three yellow cards, so track the count |
| Two-minute suspension | Player leaves the court for two minutes of playing time, team plays short | Pop-up, then a persistent countdown tile and a player-count chip |
| Third suspension, same player | Automatic disqualification | The suspension graphic chains into a red card labelled as the player's third |
| Red card (disqualification) | Player is out. The team plays short two minutes, then restores its numbers | Red card overlay plus a companion two-minute clock tagged to whoever serves it |
| Blue card | Accompanies a disqualification and signals a written report will follow | A distinct card graphic that adds no suspension time beyond the red |
| Passive play warning | The attacking side has limited passes left before losing possession | A persistent corner indicator, cleared by a shot, goal, turnover or the referee |
The player-count chip is the cheapest storytelling on the whole bug. A neutral viewer does not know why a team suddenly cannot defend the six-metre line. A chip reading 5v7 explains it in one glance, and it is derived from state the bug already holds.
Extensions worth putting on a handball bug
A scorebug extension is a stat panel that pops out of the bug on a milestone or an operator cue, then retracts. In handball, these earn their place.
- Goalkeeper save percentage. Saves divided by saves plus goals conceded. In a sport where a hot goalkeeper decides matches, it is the most explanatory number available.
- Seven-metre efficiency. Goals from attempts, per team and per shooter, and a fair predictor of how a shootout will go.
- Shooting efficiency. Goals divided by shots attempted, per player. Scorelines look similar until you see who took the shots.
- Top scorer. Goals, shots and efficiency for the match leader, refreshed on each goal.
How LIGR drives a handball scoreboard
Handball below the top tier almost never has a commercial data feed behind it. That is the central problem with buying broadcast graphics for the sport, and it is the one LIGR is built around.
Where an official feed exists, LIGR takes it. Where it does not, the LiveScore app is the feed. One person taps real match events as they happen, a goal, a seven-metre, a suspension, a timeout, and each is written with a timestamp. The graphics update from that record, and because the record exists, stat extensions and automated highlights come off the same taps. The graphics do not care which source fed them.
The bug is designed in Rive and bound to live data in Fuse, LIGR's graphics configuration engine. That matters here: a suspension tile is a data-bound element that repeats, not a hand-drawn box, so the third concurrent countdown is a state the graphic already understands rather than a redraw. Same for the player-count chip and the period pill.
Once bound, Game Plans decides when it appears. Suspension tiles mount when the event lands and retract when the countdown clears, goal graphics fire off the goal event, and break playlists run to the clock. If you want a person in the loop, the Control Room gives an operator manual control in the browser. If you do not, auto mode runs the match from the data.
Handball is on our build list rather than in our shipped render set, so we will not pretend a finished handball package is sitting on a shelf. What is true is that the hard parts, concurrent countdowns tied to named players, a derived shorthanded indicator and a clock that survives stoppages, are things the platform already does elsewhere. The same stack renders 640+ DAZN National League matches a season.
Frequently asked questions
What is a handball scoreboard overlay?
A handball scoreboard overlay is the on-screen graphic that sits over the video and carries the live match state, and broadcast people call the same graphic a scorebug. In handball it has to show the score, a count-up clock running to 30:00 and then to 60:00, the period, team timeout pips, and a two-minute countdown tile for every suspended player, plus a player-count chip whenever a team is short.
What does a handball scoreboard need to display?
At minimum: both team identities, the score, a count-up match clock running to 30:00 and then to 60:00, and the period. Beyond that, handball requires a live two-minute countdown for every currently suspended player, a player-count indicator when a team is short, and team timeout pips. Without the suspension clocks a viewer cannot tell why a team is defending with six players.
How many suspension clocks can a handball scorebug need at once?
Up to three per team at once, which is a worst case of six live countdowns on screen alongside the match clock. It is rare, but a bug with room for only one suspension per team breaks the first time it happens. The tiles also need to queue, so when one countdown expires the next starts in its place.
Does the handball clock stop for a two-minute suspension?
No. Play restarts immediately and the match clock keeps running, which is exactly why the suspension countdown has to be a separate timer. The suspension is measured in playing time, so if the referees do stop the clock for an injury, a review or a team timeout, the suspension countdown must stop with it and resume together.
What is the blue card in handball?
The blue card accompanies a disqualification and signals that the officials will file a written report on the incident, which can lead to a further sanction from the competition afterwards. On a scorebug it is a distinct card graphic shown alongside the red. It does not add extra suspension time and it does not change the player count beyond what the red card already caused.
How do you show handball timeouts on a scoreboard?
As three pips per team, drained as they are used. Each team gets three team timeouts across the match with a maximum of two in either half, so a team that has used two before half time cannot use its third until the second half. A pip row that greys out the unavailable timeout communicates that budget far better than a number.
Can you run handball graphics without a data feed?
Yes. Most handball outside the top tier has no commercial data feed, so LIGR uses its LiveScore app instead. An operator taps goals, seven-metre throws, suspensions and timeouts as they happen, each event is timestamped, and the graphics update from that record. The scoreboard renders identically whether the events came from an official feed or from the app.
Put a proper scoreboard overlay on your handball coverage
Cloud-native broadcast graphics, no hardware, no per-match operator. Start free, or talk to us about what your competition needs on screen.
Related reading
- How scoreboard graphics work across every sport
- Every sport LIGR supports
- Fuse, binding a design to live match data
- Game Plans, triggering graphics from match events and the clock
- DAZN National League, 640+ matches a season