Telegram RegisterThe public register of Telegram
Telegram profile photo for Wallet Status

Channel

Wallet Status

@wallet_status

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

74,595subscribers

-1,489 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002331538657
TypeChannel
Username@wallet_status
DescriptionTechnical & maintenance notifications for Wallet in Telegram. Support: @wallet_supportbot
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held35
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/wallet_status

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 82% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

74,59576,08475,339.56 August 2026 — 76,084 subscribers6 August 2026 — 76,084 subscribers6 August 2026 — 76,052 subscribers7 August 2026 — 76,017 subscribers8 August 2026 — 75,970 subscribers9 August 2026 — 75,935 subscribers10 August 2026 — 75,903 subscribers11 August 2026 — 75,860 subscribers12 August 2026 — 75,822 subscribers13 August 2026 — 75,796 subscribers14 August 2026 — 75,759 subscribers16 August 2026 — 75,722 subscribers17 August 2026 — 75,659 subscribers18 August 2026 — 75,611 subscribers19 August 2026 — 75,577 subscribers20 August 2026 — 75,557 subscribers21 August 2026 — 75,513 subscribers23 August 2026 — 75,453 subscribers24 August 2026 — 75,407 subscribers25 August 2026 — 75,379 subscribers26 August 2026 — 75,334 subscribers27 August 2026 — 75,312 subscribers28 August 2026 — 75,280 subscribers29 August 2026 — 75,247 subscribers30 August 2026 — 75,232 subscribers31 August 2026 — 75,189 subscribers1 September 2026 — 75,152 subscribers2 September 2026 — 75,109 subscribers4 September 2026 — 75,085 subscribers6 September 2026 — 75,001 subscribers9 September 2026 — 74,845 subscribers11 September 2026 — 74,783 subscribers13 September 2026 — 74,719 subscribers15 September 2026 — 74,678 subscribers17 September 2026 — 74,595 subscribers6 August 202617 September 2026
35 measurements spanning 42 days, net -1,489. 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 74,372–76,307 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
17 Sept 2026, 10:2074,595-83
15 Sept 2026, 06:4174,678-41
13 Sept 2026, 15:5874,719-64
11 Sept 2026, 23:3674,783-62
9 Sept 2026, 15:3774,845-156
6 Sept 2026, 07:0075,001-84
4 Sept 2026, 03:4075,085-24
2 Sept 2026, 15:5675,109-43
1 Sept 2026, 13:3775,152-37
31 Aug 2026, 15:4375,189-43
30 Aug 2026, 14:5675,232-15
29 Aug 2026, 17:3475,247-33
28 Aug 2026, 20:1375,280-32
27 Aug 2026, 17:1875,312-22
26 Aug 2026, 20:3475,334-45
25 Aug 2026, 19:2775,379-28
24 Aug 2026, 21:3575,407-46
23 Aug 2026, 09:0475,453-60
21 Aug 2026, 21:1875,513-44
20 Aug 2026, 13:5875,557first reading

Engagement

28 posts held, back to 7 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 97 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.3%
avg views ÷ 74,595 subscribers
Avg views / post
12,900
8 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
8
of 28 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 September 2026
Posts held28 (7 June 202619 September 2026)
Views total103,030
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 00:42 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.

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 23 September 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.

Recent posts

19 Sept 2026, 16:27 UTC≈8,360 viewsread 23 September 2026

✅ TON blockchain Deposits and Withdrawals restored TON blockchain deposits and withdrawals are available again and processing normally. Thank you for your patience!

19 Sept 2026, 16:13 UTC≈8,970 viewsread 23 September 2026

⚠️ TON blockchain Deposits and Withdrawals Unavailable TON blockchain Deposits and Withdrawals are currently unavailable. Your funds are safe. Our team is working to restore normal operations as soon as possible. We’ll let you know here once the issue is resolved.

18 Sept 2026, 07:28 UTC≈10,700 viewsread 23 September 2026

✅ Services restored Balances are displaying correctly again, and transactions are being processed normally. All Wallet services are fully operational. Thank you for your patience!

18 Sept 2026, 07:05 UTC≈10,600 viewsread 23 September 2026

⚠️ Balance Display and Transaction Issues Some users may currently see incorrect balances. There may also be issues with transaction processing. Your funds are safe. Our team is already working to resolve the issue. We’ll let you know here once all services are fully operational again.

16 Sept 2026, 22:24 UTC≈12,600 viewsread 23 September 2026

✅ Maintenance has been completed. All Wallet services are fully operational. Thank you for your patience!

16 Sept 2026, 18:01 UTC≈13,000 viewsread 23 September 2026

🛠 Planned Maintenance on Wallet From 16 September, 2026, 22:00 UTC to 16 September, 2026, 23:00 UTC, we'll be performing scheduled technical maintenance on Wallet. During this time we'll be improving the network infrastructure to boost stability and performance. Wallet will remain accessible, but you may experience brief interruptions, delays, or temporary unavailability of some features during this period. Don't

8 Sept 2026, 16:07 UTC≈19,900 viewsread 23 September 2026

✅ Ethereum withdrawals restored Ethereum withdrawals are available again and processing normally. Thank you for your patience!

8 Sept 2026, 14:35 UTC≈18,900 viewsread 23 September 2026

⚠️ Ethereum Withdrawals Unavailable Ethereum withdrawals are currently unavailable. Your funds are safe. Our team is working to restore normal operations as soon as possible. We’ll let you know here once the issue is resolved.

22 Jul 2026, 23:12 UTC≈32,300 viewsread 23 September 2026

✅ Maintenance has been completed. All Wallet services are fully operational. Thank you for your patience!

22 Jul 2026, 10:46 UTC≈31,100 viewsread 23 September 2026

🛠 Scheduled Maintenance for Crypto Wallet and DeFi Account From July 22, 2026, 23:00 UTC to July 23, 2026, 02:00 UTC, we’ll be performing scheduled maintenance. During this time, we’ll be carrying out network upgrades between our data centers to make the service more stable and faster. Wallet will remain available, but you may experience brief interruptions, delays, or temporary unavailability of some features dur

15 Jul 2026, 19:01 UTC≈29,200 viewsread 23 September 2026

✅ Crypto Wallet restored All Wallet services are fully operational. Thank you for your patience!

15 Jul 2026, 18:30 UTC≈29,200 viewsread 23 September 2026

🛠 Wallet is temporarily unavailable Wallet is currently unavailable due to a technical issue. Your funds remain safe and secure. Our team is working to restore the service as quickly as possible. We’ll inform you here as soon as Wallet is fully operational again.

Showing the 12 most recent of 28 posts we hold for @wallet_status. 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.

Mentions

Named by 5 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.

Names

Channels on the register whose handles appear in this channel's posts.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Wallet Status” (@wallet_status), 74,595 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/wallet_status.

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.