Futsal Scoreboard Graphics: Accumulated Fouls, Effective Time and the Scorebug Explained
What a futsal scoreboard has to carry on screen, why the foul counter is a scoreline state rather than a statistic, and how the overlay gets driven live.
A futsal scoreboard graphic must show the score, the period, an effective-time clock, each team's accumulated fouls for the current half, each team's timeout as used or unused, and the player count whenever a team is short. In a live broadcast the same graphic is also called the scorebug. Take away the foul counter and it stops describing the match, because from the sixth foul of a half onward that number decides how the next foul is punished.
Futsal looks like a compressed version of football, so it tends to get a compressed football overlay. That is the mistake. Three of the sport's rules have no equivalent in eleven-a-side, and all three belong on the bug.
What a futsal scoreboard must show
| Element | Why it matters | Source of data |
|---|---|---|
| Score | Futsal is high scoring, so the digits change often enough to need real motion design. | Goal events, feed or scoring app |
| Period and clock | Effective time. The clock stops on every dead ball, so it can never be inferred from wall time. | Timekeeper clock state |
| Accumulated fouls | Five per team per half. From the sixth onward the opposition gets a ten-metre free kick with no wall. | Foul events, reset at half-time |
| Timeout used or unused | One per team per half, and it does not carry over. A held timeout late in a half is a live tactical fact. | Timeout events |
| Player count | A sending-off leaves a team short for two minutes, or until it concedes. States like 4v5. | Derived from cards and suspensions |
| Suspension countdown | Time left on each active two-minute suspension, paused whenever the match clock is. | Card event plus clock state |
| Team identity | Crest, abbreviation and colour, fixed for the match. | Fixture data |
Accumulated fouls: the counter that changes the scoreline
This is the element that makes futsal a different graphics problem, and the one most streams leave off. Every foul punishable by a direct free kick is added to a running total for the team that committed it, held separately for each half. Indirect free kicks do not count towards it. When a team reaches five accumulated fouls, everything changes: each subsequent foul by that team gives the opposition a direct free kick from the second penalty mark, ten metres from goal, taken with no defensive wall permitted and with the kicker obliged to try to score. The attacking side can also elect to take it from where the foul occurred if that spot is nearer the goal.
In futsal, the accumulated foul counter is not a statistic. It is a persistent state that determines the punishment for the next foul, which makes it as load bearing as the score itself. A futsal scoreboard without a visible foul count is missing part of the scoreline.
Several things follow. The counter must be persistent, per team and readable at a glance, usually as five pips or a numeric chip beside each team block. It resets to zero at half-time, which makes the reset a rendering event as well as a data one. It needs a distinct alert the moment a team reaches five, because that is when the commentary, the coaching and the defending all change. And the sixth foul deserves its own graphic: a ten-metre kick with no wall is closer to a penalty than a set piece, and viewers new to futsal will not otherwise understand it.
The clock is the hard part: futsal runs effective time
A futsal match is two periods of twenty minutes, and the clock is stopped every time the ball leaves play. A timekeeper controls it, restarting when play resumes. Twenty minutes of effective time routinely takes well over half an hour in real time.
That has one large consequence. In eleven-a-side football you can drive a passable clock from the kick-off timestamp, because the clock runs continuously and added time is signalled at the end. In futsal there is nothing to derive from. The clock has to be fed from the timekeeper's state, pause and resume cleanly on demand, and it will diverge from wall time within the first minute.
Restarts make it worse in a useful way. Futsal uses kick-ins rather than throw-ins and allows four seconds to restart play, so stoppages are numerous and short. A clock that pauses sluggishly will be visibly wrong dozens of times a half.
That pause behaviour has to propagate to every other timer on screen. A two-minute suspension counts down in match time, not real time, so a sin-bin clock that keeps ticking while the match clock is stopped returns a player to the court early. Timeout countdowns, which run for a minute of real time, are the exception. Where a competition plays extra time it is two periods of five minutes, with no timeouts available.
Scoring events and what the bug does
- Goal. Score, scorer, assist where recorded, and a type chip where known: open play, free kick, ten-metre kick, penalty, corner or kick-in. If no assist was recorded the row should be absent, not a dash.
- Own goal. The opposing team's score increments, the graphic runs muted with no celebration, and the player's goal tally is not credited.
- Penalty. Taken from the penalty mark six metres out. Award, scored, missed and saved are four separate states, and saved should look different from missed because the keeper earned it.
- Ten-metre free kick. The sixth-foul kick from the second penalty mark. Distinct from a penalty and distinct from an ordinary free kick, and worth explaining on screen.
- Shootout. The clock leaves the bug entirely and a slot rail per team takes its place, filled per attempt and extended if it reaches sudden death.
Cards, suspensions and player counts
Under the FIFA Futsal Laws a yellow card is a caution and nothing more. A sending-off is what reduces a team: it plays a player short for two minutes, or until the opposition scores, whichever comes first, with the exact restoration depending on how many players each side has on court. The dismissed player takes no further part.
That gives the sin-bin countdown a property most sports do not have: two exit conditions. It can expire, or it can be cancelled by a goal. A timer that only knows how to reach zero will be wrong the moment the short-handed team concedes. Some competitions also layer a two-minute sin bin onto yellow cards, so a futsal graphic has to support both rule sets and be told which one it is running.
The player-count state itself belongs on the bug as a small chip: 4v5, 3v5, 5v4. It should update the moment a suspension starts or ends, and should never render a combination the laws do not allow.
The two states that make the closing minutes
Futsal substitutions are unlimited and flying: players change through a substitution zone with the ball in play and no stoppage required. That is the mechanism behind the fly goalkeeper, where a team pushes its keeper up as an extra outfield player for a five against four overload, leaving its own goal empty. It is legal at any point and overwhelmingly used by a team chasing a result. It also means substitution graphics must stay subtle, because a full lower third for every change would sit on screen permanently.
Late in a half three states tend to arrive together: a team is behind, it may still hold its unused timeout, and one or both sides may already be on five accumulated fouls. That convergence is why broadcasts commonly flag the closing two minutes on the bug.
Extensions: the stats worth putting on the bug
A scorebug extension is a stat panel that pops out of the bug instead of replacing it, fired automatically or by hand. In futsal the ones that earn their place are:
- Accumulated fouls, expanded. Both teams, both halves, with ten-metre kicks conceded.
- Shots on and off target. Futsal generates a high shot volume, so the split tells the story better than possession does.
- Five-a-side lineup. Court diagram with the goalkeeper flagged in a distinct jersey, and an outfielder tagged as a fly keeper when one is deployed.
How LIGR drives a futsal scoreboard
Data comes first. Where an official feed exists, LIGR takes it. Where one does not, and in futsal below the international tier there generally is not one, the LiveScore app is the feed: an operator presses the real events as they happen, goal, foul, card, timeout, substitution, each written with a timestamp. That is what makes the accumulated foul counter possible at all, because no third party will publish it for a domestic futsal league.
The overlay is data-bound in Fuse, so futsal's foul pips, clock state, timeout chip and player count are variables rather than a redraw. Animation is done in Rive and published through Fuse, rendering in HTML5, which is why the cost per match is close to nothing. Game Plans fires what should be automatic, including the alert at five fouls and the ten-metre kick graphic on the sixth; the Control Room covers anything a producer would rather call by hand.
Futsal is a sport LIGR is building out now, and the requirements above are what the graphic is built against. The same model already runs football competitions of this size, including the Corsican football league. For the wider picture see the master scoreboard graphics guide and the sport list.
Frequently asked questions
What is a futsal scoreboard overlay?
A futsal scoreboard overlay is the on-screen graphic that carries the live match state over your video feed, and in broadcast the same graphic is called the scorebug. For futsal it has to show the score, the period, an effective-time clock that pauses on every dead ball, each team's accumulated fouls for the half, the timeout chip, and the player count while anyone is serving a two-minute suspension.
What does a futsal scoreboard need to show?
Six things, permanently: both team names or crests, the score, the period and effective-time clock, each team's accumulated fouls for the current half, each team's timeout as used or unused, and the player count when a team is short. The foul counter is what separates futsal from every other football code, because at five fouls it changes how the next foul is punished.
What are accumulated fouls in futsal and why are they on the scoreboard?
Every direct-free-kick foul a team commits is added to a running total for that half. Once a team reaches five, each further foul gives the opposition a direct free kick from the second penalty mark, ten metres out, with no defensive wall allowed. The counter is not a statistic. It is a live state deciding how the next foul is punished, so it stays permanently visible.
Does the clock stop in futsal?
Yes. Futsal is played to effective time: two periods of twenty minutes, with a timekeeper stopping the clock whenever the ball goes out of play and restarting it when play resumes. Twenty minutes of effective time usually takes well over half an hour of real time, so a futsal clock cannot be approximated from kick-off. It must be driven from the timekeeper's state.
How many timeouts does each futsal team get?
One per team per period, lasting one minute, and it can only be requested when that team is in possession and the ball is out of play. An unused first-half timeout does not carry over, so each side starts the second half with one again, and no timeouts are available in extra time. On the bug that is a single chip per team.
What happens to the scorebug when a futsal player is sent off?
The team plays a player short, so the bug shows a player-count state such as 4v5. It ends after two minutes, or earlier if the opposition scores, with the exact restoration depending on how many players each side has. The countdown must pause whenever the match clock pauses, or a two-minute suspension quietly expires while the ball is dead.
Can a football scoreboard template be used for futsal?
Not as it stands. A futsal bug needs three things a football bug does not have: a per-team accumulated foul counter that resets at half-time, a clock that pauses and resumes on every dead ball rather than running from kick-off, and a player-count state driven by two-minute suspensions. Without them the overlay misrepresents the moments that decide the match.
Put a futsal scoreboard on your stream
Cloud-native broadcast graphics, driven by a feed or by your own scorer. No hardware, no operator per camera, no per-match render bill.