Telegram RegisterThe public register of Telegram
Telegram profile photo for Utorg - Crypto Card & Wallet

Channel

Utorg - Crypto Card & Wallet

@utorgapp

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

128subscribers

+27 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002166610275
TypeChannel
Username@utorgapp
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live22 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/utorgapp

Growth

101128114.58 August 2026 — 101 subscribers8 August 2026 — 106 subscribers9 August 2026 — 106 subscribers15 August 2026 — 113 subscribers22 August 2026 — 128 subscribers8 August 202622 August 2026
5 measurements spanning 15 days, net +27. 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 97–132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 20:02128+15
15 Aug 2026, 17:57113+7
9 Aug 2026, 08:47106no change
8 Aug 2026, 20:55106+5
8 Aug 2026, 00:03101first reading

Engagement

20 posts held, back to 1 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
126.9%
avg views ÷ 128 subscribers
Avg views / post
162
8 posts measured
Reaction rate
6.24%
reactions ÷ views · ER floor
Posts in window
8
of 20 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 8 August 2026
Posts held20 (1 July 20268 August 2026)
Views total1,299
Reactions total81
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 08:47 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

Video runtime
37s
Average length
7s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

180 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 40.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁7240.0%
custom 53280408735381344674122.8%
3016.7%
custom 5328010611198566539158.33%
custom 533056307590283995084.44%
63.33%
custom 533019465360819259942.22%
👍42.22%

Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 180reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 1 July 2026 to 8 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

8 Aug 2026, 11:06 UTC50 views11 reactionsread 9 August 2026
Photo

This man is number one in the world at something 👀 It's not crypto We work together now, any guesses?

6custom 53280408735381344675

7 Aug 2026, 10:59 UTC165 views8 reactionsread 9 August 2026

You get in a taxi at 11am on a Friday. The driver asks what you do for work. You say you work in crypto. He says "ah, got it, so you don't work" 😐 What would you say back?

😁8

5 Aug 2026, 13:11 UTC199 views2 reactionsread 9 August 2026
Video

Developers, we know you are not leaving the house. We left 🫡 here is what we found for you

😁2

31 Jul 2026, 09:13 UTC234 views14 reactionsread 9 August 2026

New CMO just spawned. Andrey's first executive decision as CMO: keep letting whoever writes these posts keep writing them. Visionary leadership ✨

😁64custom 53280408735381344674

30 Jul 2026, 15:18 UTC213 views19 reactionsread 9 August 2026
Video

Our new CMO. Ex-Binance 🔥 Now with us Your ad auctions are about to get more expensive, sorry in advance 💰

😁8custom 53280408735381344676custom 53280106111985665395

30 Jul 2026, 11:53 UTC165 views13 reactionsread 9 August 2026

We hired a CMO! Haven’t told him about what we post in this channel yet 😏 Soon he finds out Bring snacks 🏃‍♀️

custom 532804087353813446710custom 53305630759028399503

28 Jul 2026, 18:00 UTC148 views8 reactionsread 9 August 2026
Video

Remembered, we post about crypto here Here's your reminder to check on your seed phrase today, because somewhere, someone is watching this and not laughing 😬

custom 53280106111985665398

28 Jul 2026, 18:00 UTC125 views6 reactionsread 9 August 2026
Photo

Wait, what was this channel even about 👀

😁6

13 Jul 2026, 15:37 UTC166 views9 reactionsread 9 August 2026
Photo

🖥 we hired a junior training is going well

😁9

10 Jul 2026, 15:12 UTC169 views7 reactionsread 9 August 2026

anyway, 3 weeks in and you're still here That says more about you than us. Bring someone 📱

custom 53301946536081925994custom 533056307590283995021

10 Jul 2026, 15:10 UTC150 views6 reactionsread 9 August 2026
Photo

We worked like maniacs these weeks. Found 2 mins to brag about it 😬 Not saying what's coming, but it will be 👀🔥🔥🔥 Go sleep for us this weekend, someone should and it's not going to be us

😁6

10 Jul 2026, 15:04 UTC133 views8 reactionsread 9 August 2026
Video

decrypt in the comments what traffic light says 🫆👀 you have one free attempt

6custom 53280408735381344672

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

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

“Utorg - Crypto Card & Wallet” (@utorgapp), 128 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/utorgapp.

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.