CricketOne

In club, school, junior and friendly games, yes for the calls it can see: bowled, hit wicket, run-outs, stumpings, no-balls, wides and the over. Catches are the players' call and LBW is evidence only. Below its confidence line it says unsure and the captains check the clip.

It is built to MCC Law 8 sizes: stumps 28 in high and 1.38-1.5 in across, a 9 in wicket, bails no more than 0.5 in above the stumps. Leagues still decide in their playing conditions whether stump cameras and sensors may be used; we do not claim any governing body approval.

Yes. The 2026 Laws (in force from 1 October 2026) say a hand breaking the wicket must hold the ball with complete control, and change hit wicket for a batter who hops off balance after the shot. The run-out, stumping and hit-wicket calls check both, and say unsure when the stumps cannot see the ball held. The wicket's size did not change.

Stump cameras record video for someone to review later. CricketOne makes the call itself in under 2 seconds, lights it on the stumps and signs it in the log, and still keeps the clip for every call.

Each stump is sealed to an IP67 target with no open port, and a waterproof vent stops the seals being pumped. The windows shed water and do not fog. The LiFePO4 cells keep about 85 % at 5 °C (est.) and never charge below 0 °C. If dew or mud covers a window, the app asks for a wipe and the calls that need that view are marked unsure.

Into a thin aluminium lining inside the top of the stump, then out through the wall. The computer is clamped to an aluminium bar bonded to that lining, it runs flat out only during each delivery, and the stump is white because the sun brings more heat than the electronics. Our heat model rates every call to 38 °C air in still air and 45 °C in a light breeze, in full sun (est.); an 8-hour 45 °C chamber test checks it.

At 90 mph the ball reaches the batter in about 0.44 s, so a normal 30 fps camera sees it only every 1.34 m. Each stump has a global-shutter camera at 120 fps full frame and 200+ fps in a delivery (est.). The six shutters are staggered, so the pair looks at the ball about 1,200 times a second, one look every 34 mm. A physics model of the flight joins the points. The bounce fixes how far down the pitch the ball was, and LBW stays evidence for the umpire until field tests rate it. A track counts as sure only when two standard deviations of its own uncertainty are within ±12.5 mm at the stumps (row P14): in 400 simulated deliveries every sure track was within 6.7 mm, and about 3 in 10 deliveries were sure; the rest are marked unsure and go to the umpire.

The bails rest in plain grooves with nothing magnetic pulling on them, and the stumps keep Law 8 size. Each stump is heavier than ash: about 950 g against about 650 g (row P6, est.). Most of the extra weight sits low, so the top of a clipped stump moves about 0.78 times as fast as ash. We will prove how it plays with ball-machine and drop tests, and ask umpires and keepers in the buyer review.

$1,990 for both wickets and the charging case, with a local app and no plan needed. It replaces CreaseCam, SmartStump Pro, LengthLock, PitchTally (cricket) and Cricket MatchKit, which are $4,154 bought separately. An extra wicket pair for the nets or a second pitch is $1,490.

About 14 hours per stump at 20 °C and about 12 hours at 5 °C (est.): a full 50-over day with margin. Between sessions the six stumps stand in the charging case, which charges them through flush pads, only between 0 and 45 °C.

Every call is signed in a secure element inside the stump and kept in a log the app can check. Radios are paired and encrypted, updates are signed and never run during a match, and opening a stump marks the log.

In league matches, yes: the wicket gives evidence and a suggested call, and only umpires open a review, unless the league allows it to decide. In club, school, junior and friendly games it makes the calls it can see, and the umpire or captains take every unsure call.

The window is 1.5 mm toughened glass on a ledge inside the stump's round profile, backed by an aluminium lining, so a hit pushes it into the stump wall, never into the lens. Our impact calculations showed a plastic window would crack, so it changed. It is a replaceable part, and the stump re-aims its camera after any knock. Our ball-cannon test fires 500 balls at every stump, including straight at the window, before any pilot.

That is our target. Our hand calculations showed a plain 3 mm plastic tube is only about a quarter as strong in bending as a solid ash stump, so the ball-test stumps use a glass-fibre tube that comes out about 1.25 times as strong as ash (est.). Coupons are bent side by side with ash stumps before full stumps are made, and every result is published.

Each stump has its own small computer and clock, linked by Wi-Fi. Our simulation of a full match day found that plain Wi-Fi time sync is about 0.512 ms out, enough to halve the sure ball tracks, so CricketOne syncs carefully: 16 time checks a second keeping the fastest, a real-time system, and a light-flash check at each break where one wicket's call lights flash and the other wicket's cameras find the flash. That holds the stumps to about 0.005 ms (simulated), and the bench test measures it. If a stump loses sync, calls that need both wickets go to the umpire.

Each camera re-finds its own aim in the still half-second between deliveries, from what the Laws already put on the pitch: the far stumps and bails, which are the target itself, and the painted creases. Our simulation found that this holds the aim to about 0.003° side to side and 0.005° up and down (simulated), inside the 0.01° the ball tracking needs. It needs two factory steps on every stump: calibrating the motion sensor and the camera lens. A stump that is knocked re-aims before the next ball; if the far wicket is down at the same time, its calls go to the umpire until both are standing.

Phase 3 is a design review with the people who would use it: club chairs, league secretaries, club umpires, wicket-keepers and a nets coach (kinds of role, never named people). We show them our numbers as they are, including the open ones: a smart stump is about 950 g against about 650 g for ash and swings about 0.78x as fast when only clipped (est.), about 3 in 10 deliveries give a sure ball track with the stricter P14 rule (simulated), and LBW evidence is always unsure under club floodlights. Their answers decide how close to ash it must play, how many unsure calls are acceptable, and whether $1,990 is the right price. Junior players are never interviewed or filmed.

A small magnet sits in each bail spigot and a sensor under each groove measures its field. The moment a bail loses all contact with the stumps, the field drops and the stump logs the time, within about 0.278 ms in our simulation. That matters for run-outs, because the bat moves about 6 mm every millisecond. Our first design used an on/off magnetic switch, which we found could log the wicket 10.75-39.568 ms late, so we changed it. A bail that is only nudged and settles back is not counted as the wicket broken.

The Law asks where the front foot lands, not where it ends up, and a fast bowler's foot often slides over the line after landing fairly. Two cameras in the bowler's-end stumps follow the heel down and fit the exact spot it lands. Their shutters are staggered and they read faster for the moment of landing, so the spot is within ±2.6 mm at 95 % in our simulation, and they are sure on about 98 % of landings near the stumps. It calls only when that spot is clearly clear of the line; for bowlers who land wide of the crease, the outer stump camera on that side, turned out a little, and the far stumps' cameras find the spot together (93 % of those landings in our simulation). When the heel is flat on the ground, that outer camera places it by itself, within ±12 mm at 95 %, and the far stumps check it is not raised; a raised heel can only look further forward, so a no-ball there needs both views to agree. That makes it sure on about 92 % of those landings, with no wrong sure calls in our simulation. Close ones stay with the umpire.

Yes, from the far end. The back foot must land inside the return crease without touching it, beside the bowler's own stumps, where those stumps' cameras cannot see. The three cameras in the striker's stumps, 20 m away, see it past the batter on 92.2 % of landings in our simulation, and place the foot's outer edge against the line within ±18 mm at 95 %: they find where the sole meets the ground along its whole edge, read the painted line right at the foot and learn the bowler's own shoe from earlier balls. It calls only when the foot is clearly inside or clearly over; close ones, and feet hidden by the batter's pads, stay with the umpire.

A few millimetres, when two of the three stump cameras at that end see the bat. Taking the last frame before the bail came off would not do: at 180 frames a second a sliding bat moves 17-44 mm between frames. So the stumps follow the bat through every look from all three cameras (540 a second) and fit when it crosses the crease and when it touches down, against the moment the bail loses contact. In our simulation that is within 10.2 mm at 95 % for run-outs and 3.9 mm for stumpings, with no wrong sure calls. The two outer stump cameras are turned out a little, for bowlers who land wide of the crease, so the stumps now see run-outs up to about 1.4 m wide (0.95 m before); the price is that fewer bats are seen by all three cameras, so the fit is a little looser than the 6.5 mm we had with all three facing straight. A bat seen by one camera only, a batter running wider still, or a fielder standing in the way is unsure, and the umpire checks the clip.

A bail coming off is not enough: the keeper can knock it off for a stumping, or the ball can hit the keeper first. The stumps call bowled only when three things agree: the bail goes off and stays off, it goes within a few hundredths of a second of the ball track reaching the stumps, and the motion sensor in the struck stump feels the ball hit (or the ball clearly clipped only the bail). A ball off the bat or pad still counts, as Law 32 says. In 20,000 simulated close deliveries that was sure on 97.5 % of bowled balls with no wrong sure calls; light grazes go to the umpire as unsure. Using the bail alone would have got about 1 in 10 wickets-down wrong.

About half the time, and it says so. The batter's own stumps face up the pitch, so only the far stumps, 20 m away, can watch the batter, and the batter's body often hides a back foot or pad behind the stumps. The stumps call out only when four things agree: the far cameras see the bat, body or a fallen helmet nearest the stump that was hit, it happened before the batter regained balance after the shot (the 2026 Laws), the ball was not a no-ball, and no fielder was within a metre. In 20,000 simulated cases that was sure on 47.8 % of hit wickets with no wrong sure calls; the rest show unsure and the umpire or captains watch the clip. Reading the stump hit and one view of balance alone, as we first planned, got 12.0 % wrong.

It counts only valid balls, as Law 17 says: a ball the bowler did not deliver, a dead ball before the batter could play, a wide or a no-ball does not count. The stumps see each delivery stride, release and ball track, and the bail sensors see a bail fall before the ball. When they are not sure whether a ball was a wide or a no-ball, they ask in the app before the next ball: the umpire taps their own call in the app on their phone, or the scorer enters the umpire's signal; with no umpire, the scorer answers from a 10-second clip and the batting side can challenge until the over is called. In our simulation of club overs at 16 an hour, the scorer's answer from the umpire's signal came before the next ball 98.9 % of the time, and 87 % with no umpire; a ball still unanswered is never guessed, and play never had to wait. In 20,000 simulated overs that put the blue light on the right ball 99.3 % of the time; a counter that guessed every close ball got about 38 % of overs wrong. Today it asks about 0.67 balls an over (1.38 before rows P31 to P33 sharpened the front-foot and back-foot calls), mostly back feet close to the return crease; leg-side wides need only about 0.09 an over, and the front foot of bowlers who land wide of the crease no longer needs asking unless it is close.

Club limited-overs games paint an off-side wide guideline about 888 mm from middle stump. The six stump cameras follow the ball after it bounces and on past the stumps, and fit where it crossed the popping crease: within about 1.6 mm at 95 % and 2.6 mm at worst in our simulation of 400 deliveries, with no wrong sure calls. The close ones turn on the Law, not the line: if the striker moved the ball into reach or it touched the bat or the batter, and the stumps are not sure which, they say unsure and the umpire or captains decide. Down the leg side the line is the leg stump and the hard part is a touch: the stumps compare the track before and after the batter, place the pads and bat from the far cameras, and call a wide only when the ball was clearly outside leg stump and clear of both. In 600 simulated leg-side balls that was sure on 83 % with no wrong sure calls; the track alone got 2.8 % wrong. Matches that play MCC Law 22 judge the leg side on reach instead, so you choose the rule when you set up the match: the far stumps place the batter and their normal guard, estimate their reach from their height, and call a wide only when the ball was clearly out of reach from both. In 20,000 simulated balls that was sure on 86 % with no wrong sure calls; using the leg-stump line in such a match would have got 81.1 % wrong. Simulated only; bench and nets tests come next.

No. CricketOne is our first product and is in phase 2, engineering: making the design accurate, safe and to standards before it is built. Specifications are targets. We are not taking orders, reservations or deposits, and it has no ship date yet.

So the stumps can see the front foot of bowlers who land wide of the crease. Turning those two cameras sees more wide landings but puts fewer points of the batting crease in all three cameras, so slightly fewer run-outs and stumpings are sure. We simulated seven angles from 0° to 14° and counted how often a club match would need the umpire or captains to answer a call the stumps were not sure of: about 136 times facing straight, about 112 at 12°, the fewest. 10° is close and would win only if an unsure run-out counts as much as about six unsure balls, which we will ask umpires. An angle that made even one wrong sure call in the simulation was ruled out. These are simulated numbers with an estimated match mix, checked on the first units.