Channel
@TelePayStatus
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
15subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001810865445 |
|---|---|
| Type | Channel |
| Username | @TelePayStatus |
| Description | Operational status updates of @TelePayCash. |
| Created | 5 March 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/TelePayStatus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 23:16 | 15 | no change |
| 11 Aug 2026, 07:15 | 15 | first reading |
7 posts held, back to 5 March 2023 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 29 April 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Dear community, We have taken the hard decision of closing TelePay. If you have any funds in the platform, please, log in and request to withdraw all of your funds before May 29th. We will shut down the platform that day. If you would like to learn more about this decision, read our announcement: https://blog.telepay.cash/the-end Thank you for your understanding.
✅ Incident: TON deposits The incident has been solved. Deposits and withdrawals over TON has been activated again. Apologies for the interruption.
⏺ Incident: TON deposits The tonscan.org team seem to have noticed the problem with their explorer. It now lists all transactions. Researching about the provider we use to confirm deposits. We will keep you updated.
⏺ Incident: TON deposits The tonscan.org explorer is not showing up the latest transactions in users' wallets, or any of our wallets. The firs image shows TonScan not listing today's transactions. The second image shows dton.io explorer showing all transactions. Preliminary conclusion: the blockchain is operating normally and our internal mechanism to forward the tokens too. Researching about the provider we use…
⏺ Incident: TON deposits We are investigating an incident related to TON deposits. Our main blockchain provider seems to be offline and not responding to our requests. Deposits and withdrawals from TON have been deactivated temporarily, until we figure out what's happening. Will keep you updated.
Channel photo updated
Channel created
Showing the 7 most recent of 7 posts we hold for @TelePayStatus. 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 — 843,670 of 1,622,561entries 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“TelePay Status” (@TelePayStatus), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/TelePayStatus.
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.