Telegram RegisterThe public register of Telegram
Telegram profile photo for London potato's Arbitrage

Channel

London potato's Arbitrage

@londonpotato

On this record: Growth · Engagement · Posts · Citations · Cite this entry

1,397subscribers

+7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003890886317
TypeChannel
Username@londonpotato
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/londonpotato

Growth

1,3901,3971,393.56 August 2026 — 1,390 subscribers6 August 2026 — 1,390 subscribers9 August 2026 — 1,391 subscribers13 August 2026 — 1,393 subscribers16 August 2026 — 1,397 subscribers6 August 202616 August 2026
5 measurements spanning 11 days, net +7. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,389–1,398 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 18:171,397+4
13 Aug 2026, 05:241,393+2
9 Aug 2026, 20:571,391+1
6 Aug 2026, 07:511,390no change
6 Aug 2026, 02:371,390first reading

Engagement

17 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
71.8%
avg views ÷ 1,397 subscribers
Avg views / post
1,000
17 posts measured
Reaction rate
0.806%
reactions ÷ views · ER floor
Posts in window
17
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 10 of 17 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held17 (27 July 20266 August 2026)
Views total17,043
Reactions total81
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 07:51 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

6 Aug 2026, 05:31 UTC≈274 views1 reactionsread 6 August 2026

청원 글 잘쓰는 사람 어디 없나 물론 아무것도 안 하는 나보다 백배 천배 낫지만 청원올라오는 글들을 읽어보면 대부분 감정이 꽤 많이 섞인 글에 전문적이지가 않아서 .. 위에서 법안 검토하는 사람들이 콧방귀라도 뀌어줄까 싶네

31 Jul 2026, 09:26 UTC≈769 views1 reactionsread 6 August 2026

토일월화수목금 7일연상에 레상이 단 한개도 없었던 건에 대하여

30 Jul 2026, 14:28 UTC≈1,420 views2 reactionsread 6 August 2026
Photo

adr vs 하닉본주 레갭 발생 https://adr-gap-chart-production.up.railway.app/

30 Jul 2026, 06:37 UTC≈1,000 views5 reactionsread 6 August 2026
Photo

🚨빗썸 고객확인 서류를 모두 제출했지만 서비스 이용제한(영구정지) 예정 통보를 받았습니다. ✍️한 줄 요약 반복적인 코인 출금으로 고객확인 요청 및 출금정지 조치를 받은 후 요청받은 모든 서류를 제출했지만, 추가 소명 기회 없이 '자금출처 확인 불충분'을 이유로 1개월 후 빗썸 서비스 이용제한(영구정지) 예정 통보를 받았습니다. 📅진행 경과 6월 30일: 반복적인 코인 출금 관련 1차 주의 안내 문자 수신 7월 1일: 반복적인 코인 출금 관련 2차 주의 안내 문자 수신 7월 3일: 고객확인 요청 및 출금정지 안내 문자 및 메일 수신 7월 6일: 추가 서류 제출 요청 안내 메일 수신 7월 7일: 모든 서류 제출 완료 7월 24일: 자금출처 확인 불충분을 이유로 1개월 후 빗썸 서비스 이용제한(영구정지) 예정 안내 메일 수신 💰거래 방식 및

29 Jul 2026, 09:59 UTC≈791 views1 reactionsread 6 August 2026
Photo

양이온만 있거나 음이온만 있나보다.. 이온결합이 전혀 일어나지 않는 모습이다... 아무도 화학반응에 참여하지않고있다...

29 Jul 2026, 09:36 UTC≈792 views2 reactionsread 6 August 2026
Photo

그러니까 안전한 코인이나 하자고요.. 디지털금이라니까요

28 Jul 2026, 14:47 UTC≈863 views5 reactionsread 6 August 2026
Photo

https://ntt-rate-checker-production.up.railway.app/ NTT rate limit checker 별건아니고 필요할때 사용하시면 좋을거같네요 list에 원하는 토큰이없으면 Custom 클릭하고 CA 입력해서 사용하면 됩니다

28 Jul 2026, 07:56 UTC≈1,480 viewsread 6 August 2026

빗썸 알트코인 출금으로 고객확인 요청받고 출금정지되거나 심사후에 자금출처 확인 불가하다고 영구정지 당하신분들 의논하고 대책마련하는 그룹 만들었는데

Showing the 12 most recent of 17 posts we hold for @londonpotato. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Citation-graph rank

Citation-graph rank — 80,557 of 1,481,502entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 16 August 2026 — this entry's latest reading, not the date you are reading this.

“London potato's Arbitrage” (@londonpotato), 1,397 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/londonpotato.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.