LottoEcho LottoEcho
Log in Create Account
Who it's for
Who it's for

For anyone who keeps a record of numbers, and wishes to understand it.

LottoEcho was made for lottery results, yet the same questions arise wherever numbers recur: which appear most often, which have fallen silent, and which tend to arrive together.

01Lottery players
01 · Lottery players

Those who keep their own selections, week after week.

I have played the same six numbers for two years. How have they actually done?

Results arrive on their own for the lotteries we follow. Your tickets are marked after every draw, and the running history replaces memory with a record.

  • Frequency and dormancy for any period
  • Every ticket marked automatically
  • A history of how each selection has fared
Your selection · last 6 draws
4 Nov317232941443/6
31 Oct317232941443/6
28 Oct317232941442/6
24 Oct317232941442/6
21 Oct317232941442/6
17 Oct317232941443/6

This selection matched 15 numbers across 6 draws, never more than 3 at once.

Defect codes · last 12 batches

D-17 appeared in 9 of 12 batches; D-31 has been absent from the last 8.

02Quality and production
02 · Quality and production

Teams who log defect codes, batch after batch.

Which faults keep returning, and which have we genuinely resolved?

Treat each batch as a draw and each defect code as a number. Recurring codes rise to the top; those that have not appeared for weeks are ranked by how long they have been absent.

  • Codes that recur across batches
  • Codes gone quiet, and for how long
  • Codes that tend to appear together
03Operations and on-call
03 · Operations and on-call

Engineers who record which services alert during each incident.

When the payments service fails, what else tends to fail with it?

Each incident becomes a result; each node or service a number. Pairs that keep appearing together show where one failure is really another in disguise.

  • Services that alert together
  • The usual shape of an incident
  • Which ones have stopped appearing
Seen together · last 40 incidents
payments+auth-gw 14
queue-02+search 9
auth-gw+cdn-edge 6
mail+queue-02 3

payments and auth-gw alerted together in 14 of 40 incidents.

Sold out · last 8 weeks
MonTueWedThuFriSatSunSourdoughOat milkEggsCut flowers

Sourdough sold out on 7 of the last 8 Saturdays.

04Retail and inventory
04 · Retail and inventory

Shops that note which lines sold out, day by day.

Do we always run short of the same things on the same days?

Each day is a result; each product line a number. The weekly rhythm of shortages becomes visible, as does the moment it begins to shift.

  • Lines that run out most often
  • The days on which they do
  • How that pattern changes over a season
Side by side
Side by side

One method, read four ways.

A result is A number is Frequency shows Your picks are
Lottery players a draw a ball which numbers recur your tickets
Quality and production a batch a defect code which faults return codes you are watching
Operations and on-call an incident a service which services fail most your critical services
Retail and inventory a day a product line which lines run out this week's order
In fairness
In fairness

What LottoEcho is not.

Not a prediction service Past results do not foretell future ones. LottoEcho describes what has happened; it makes no promises about what will.
Not a betting service We sell no tickets, take no stakes and handle no payments of any kind.
Not for anyone under 18 Every account confirms its holder's age at registration.

Whichever numbers you keep, they already have a shape.

Registration takes three details and about half a minute.