Telegram RegisterThe public register of Telegram
Telegram profile photo for payloud

Channel

payloud

@payl0ud

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

307subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002642277803
TypeChannel
Username@payl0ud
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/payl0ud

Growth

307308307.57 August 2026 — 307 subscribers8 August 2026 — 307 subscribers15 August 2026 — 308 subscribers22 August 2026 — 307 subscribers7 August 202622 August 2026
4 measurements spanning 15 days. 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 307–308 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 17:09307-1
15 Aug 2026, 04:28308+1
8 Aug 2026, 07:48307no change
7 Aug 2026, 18:14307first reading

Engagement

20 posts held, back to 5 October 2025the 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
30.9%
avg views ÷ 307 subscribers
Avg views / post
94.9
7 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
7
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. It is computed over the 1 of 7 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 4 August 2026
Posts held20 (5 October 20254 August 2026)
Views total664
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 07:48 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.

Reaction mix

79 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 22.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 59245577315444381501822.8%
👍1519.0%
1215.2%
😢1012.7%
🤡78.86%
🔥67.59%
😁67.59%
🤣22.53%
🐳11.27%
👀11.27%
👏11.27%

Custom emoji. One row above is a 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 count beside it isTelegram’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 14 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 79reactions 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 5 October 2025 to 4 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

4 Aug 2026, 06:27 UTC49 views0 reactionsread 8 August 2026
Photo

$MAX 0x338dd2dad3B4ddf5e85A05AD89A12C23985c1AE0 Jeff's dog's name. Launched on a new launchpad @MotionOnHype source: https://colossus.com/article/beyond-the-sky-jeffrey-yan-hyperliquid/ ***launchpad rugged...

Signed payloud

31 Jul 2026, 08:30 UTC104 viewsread 8 August 2026

@arc alpha 1) $ARCANINE (0xf3715bf5c2de299f08b81180ffb739a8372a175f) - First token on Arc; 2) $USDC (0x0006ed5d37a9d6687d1ecc8b642ff9c4760d9a16) - lore - https://x.com/USDC/status/2016182551837278550?s=20 3) $BIRDIE (0x8e604ae97dda3deb77d9856606a8dc3135998fc4) lore - https://x.com/chrisries/status/1988805902657548855?s=20 4) $STEVE (0x3db49a7d8c6632ba04dd83e9e51147bc35c3499f) lore - https://x.com/USDC/status/2077489

Signed payloud

30 Jul 2026, 13:22 UTC94 viewsread 8 August 2026

https://basedbot.app/token/arc/0xf3715bf5c2de299f08b81180ffb739a8372a175f

Signed payloud

29 Jul 2026, 21:36 UTC108 viewsread 8 August 2026

Added support to the bot, now you can get USDC in Arc

Signed payloud

29 Jul 2026, 21:35 UTC106 viewsread 8 August 2026

✅ Bridge completed successfully Received on Arc: 13.9 USDC Current Arc balance: 13.9 USDC Wallet: 0xd05CdEc33fd2F290620Eb0B98EF6f77B2589b91A Arc transaction: 0x8d4a92990a2b412cbb96f4d5e39c7a2d95f5881f1848c16ecdd7257d081d2c78 Your USDC is ready to use on Arc.

Signed payloud

19 Jul 2026, 11:40 UTC208 views5 reactionsread 8 August 2026
Photo

I built Arctic Snipe — an automated bridge and token sniper for Arc. The problem: when the Arc bridge opens, being first means watching it 24/7 and reacting in seconds by hand. Most people miss the window. What it does: the moment the bridge goes live, Arctic Snipe (https://x.com/arcticsnipe) automatically bridges your funds from Ethereum to Arc and instantly buys up to 3 tokens of your choice by contract. Set your

3custom 59245577315444381502

Signed payloud

27 Apr 2026, 11:06 UTC396 views15 reactionsread 8 August 2026
Photo

Sup guys! I've been out of the market for a long time, as there's not much activity at the moment, and everything I've done is what I described in detail earlier. I decided not to waste time and started working on my own project called "Astra Markets". It will be a Trading Terminal inside Telegram, where it will be possible to trade: Prediction Markets, Crypto, RWA, FX, Pre-IPO, and so on, as well as built-in AI for

👍6🤡3😁3🤣2🔥1

Signed payloud

22 Jan 2026, 11:19 UTC546 views0 reactionsread 8 August 2026
Photo

100k points on Hibachi (spending ~$800 on fees) link: https://hibachi.xyz/r/1 It's been a few months since I found Hibachi and wrote about it. After a long time of lull, the volumes began to grow again (for a long time the daily volume was ~5-10M now 50M+), I noticed that CT began to write more and more about Hibachi and there are reasons for this: 1) Of course it's a Perp DEX meta (don't forget that Hashflow is b

Signed payloud

21 Jan 2026, 05:09 UTC379 views2 reactionsread 8 August 2026
Photo

Got 3000 Nado points from Private Alpha It's funny, but I knew in advance the exact time when the "The Choice" menu would be available, but I overslept anyway, so I would have chosen NFT (loyalty is always encouraged), but in the end, of course, I chose Points without hesitation. My stats: Started trading - November 27th / burned $2500~ / 5m volume + 13m volume from refs What we have now 1) You have exactly one w

custom 59245577315444381502

Signed payloud

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

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

“payloud” (@payl0ud), 307 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/payl0ud.

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.