Telegram RegisterThe public register of Telegram
Telegram profile photo for REP Channel

Channel

REP Channel

@replabs

Not marked by Telegram, checked 2 September 2026

On this record: Topic · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry

1,481,426subscribers

-151,070 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002425693690
TypeChannel
Username@replabs
Description@repcoinbot
Created28 September 2024 — measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/replabs

Topic

Technology — 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 8 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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

1,481,4261,632,4961,556,9616 August 2026 — 1,632,496 subscribers6 August 2026 — 1,632,496 subscribers7 August 2026 — 1,630,516 subscribers8 August 2026 — 1,628,687 subscribers9 August 2026 — 1,626,335 subscribers10 August 2026 — 1,623,983 subscribers10 August 2026 — 1,622,151 subscribers11 August 2026 — 1,620,008 subscribers13 August 2026 — 1,617,800 subscribers14 August 2026 — 1,615,612 subscribers15 August 2026 — 1,612,400 subscribers17 August 2026 — 1,609,130 subscribers18 August 2026 — 1,606,990 subscribers19 August 2026 — 1,604,994 subscribers20 August 2026 — 1,602,939 subscribers21 August 2026 — 1,600,957 subscribers22 August 2026 — 1,596,856 subscribers24 August 2026 — 1,592,571 subscribers25 August 2026 — 1,588,567 subscribers26 August 2026 — 1,585,572 subscribers27 August 2026 — 1,584,745 subscribers28 August 2026 — 1,580,371 subscribers29 August 2026 — 1,574,876 subscribers30 August 2026 — 1,570,238 subscribers31 August 2026 — 1,565,523 subscribers1 September 2026 — 1,559,433 subscribers2 September 2026 — 1,552,926 subscribers4 September 2026 — 1,547,923 subscribers6 September 2026 — 1,535,497 subscribers9 September 2026 — 1,518,586 subscribers12 September 2026 — 1,509,994 subscribers13 September 2026 — 1,498,852 subscribers15 September 2026 — 1,491,302 subscribers17 September 2026 — 1,481,426 subscribers6 August 202617 September 2026
34 measurements spanning 43 days, net -151,070. 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,458,766–1,655,157 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
17 Sept 2026, 23:211,481,426-9,876
15 Sept 2026, 17:181,491,302-7,550
13 Sept 2026, 21:411,498,852-11,142
12 Sept 2026, 03:201,509,994-8,592
9 Sept 2026, 21:191,518,586-16,911
6 Sept 2026, 16:401,535,497-12,426
4 Sept 2026, 04:171,547,923-5,003
2 Sept 2026, 15:341,552,926-6,507
1 Sept 2026, 16:271,559,433-6,090
31 Aug 2026, 19:551,565,523-4,715
30 Aug 2026, 18:551,570,238-4,638
29 Aug 2026, 17:471,574,876-5,495
28 Aug 2026, 18:331,580,371-4,374
27 Aug 2026, 20:481,584,745-827
26 Aug 2026, 19:071,585,572-2,995
25 Aug 2026, 17:281,588,567-4,004
24 Aug 2026, 17:031,592,571-4,285
22 Aug 2026, 21:481,596,856-4,101
21 Aug 2026, 11:371,600,957-1,982
20 Aug 2026, 11:531,602,939first reading

Engagement

180 posts held, back to 28 September 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 265 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.255%
avg views ÷ 1,481,426 subscribers
Avg views / post
3,780
2 posts measured
Reaction rate
0.556%
reactions ÷ views · ER floor
Posts in window
2
of 180 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 4 September 2026
Posts held180 (28 September 2024 – 4 September 2026)
Views total7,560
Reactions total42
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 05:20 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

Photos
89
Videos
11
Links
134

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

Video runtime
4m 41s
Average length
35s

Measured directly from 8 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.

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 5 of this channel’s own posts over the last 30 days: across 5 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 21 hours of being posted; a typical post has already reached 33.5% of its 24-hour view count within the first hour, and 69.7% within the first six; the median 24-hour reach across those posts is 1,110 views — 0.073% of this channel’s own subscriber count (90th percentile 1,248).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/1944 Sept 2026, 16:08 UTC12033 minutes – 7 days old2,800 views ~9 reactions60 minutes: 505 interp. → 3.0 hours: 760 → 6.0 hours: 893 → 12 hours: 1,000 → 24 hours: 1,280 → 2 days: 1,530 → 7 days: 2,800still climbing at last reading1,280measured37 hours
/1931 Sept 2026, 16:58 UTC12223 minutes – 7 days old2,290 views ~28 reactions60 minutes: 363 interp. → 3.0 hours: 569 → 6.0 hours: 702 → 12 hours: 816 → 24 hours: 1,110 → 2 days: 1,320 → 7 days: 2,290still climbing at last reading1,110measured27 hours
/19225 Aug 2026, 16:54 UTC11156 minutes – 7 days old2,280 views ~17 reactions60 minutes: 370 interp. → 3.0 hours: 607 → 6.0 hours: 743 → 12 hours: 868 → 24 hours: 1,200 → 2 days: 1,460 → 7 days: 2,100still climbing at last reading1,200measured21 hours
/19114 Aug 2026, 14:06 UTC9510 minutes – 7 days old1,700 views ~15 reactions60 minutes: 305 interp. → 3.0 hours: 504 → 6.0 hours: 636 → 12 hours: 727 → 24 hours: 910 → 2 days: 1,120 → 7 days: 1,700still climbing at last reading910measured20 hours
/19011 Aug 2026, 12:11 UTC11839 minutes – 7 days old2,440 views ~8 reactions60 minutes: 327 interp. → 3.0 hours: 495 → 6.0 hours: 636 interp. → 12 hours: 761 → 24 hours: 913 → 2 days: 1,100 → 7 days: 2,440still climbing at last reading913measured3 days
/18910 Aug 2026, 18:30 UTC10851 minutes – 7 days old2,690 views ~8 reactions60 minutes: 440 interp. → 3.0 hours: 671 interp. → 6.0 hours: 823 → 12 hours: 1,040 → 24 hours: 1,530 → 2 days: 1,730 → 7 days: 2,690still climbing at last reading1,530measured18 hours
/1887 Aug 2026, 19:19 UTC141under a minute – 7 days old4,950 views ~15 reactions60 minutes: 575 → 3.0 hours: 918 → 6.0 hours: 1,160 → 12 hours: 1,640 → 24 hours: 2,270 → 2 days: 2,900 → 7 days: 4,950still climbing at last reading2,270measured32 hours
/1877 Aug 2026, 13:15 UTC138under a minute – 7 days old4,940 views ~12 reactions60 minutes: 345 interp. → 3.0 hours: 546 → 6.0 hours: 689 → 12 hours: 1,610 → 24 hours: 2,320 → 2 days: 3,010 → 7 days: 4,940still climbing at last reading2,320measured28 hours

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

431 reactions across 28 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🌚431100.0%

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 178 of the 180 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 248,527 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 180 most recent posts we hold, published 28 September 2024 to 4 September 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.

Telegram Stars

Stars received
193
across the posts below
Posts paid on
11
of 178 we hold a reading for · 6%
Most on one post
70
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @replabs. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 180 most recent posts we hold for this entry, published 28 September 2024 to 4 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

4 Sept 2026, 16:08 UTC≈4,280 views13 reactionsread 27 September 2026
Photo

the first offer ever placed in matches is live: polymarket perps affiliate program. affiliate deals used to be negotiated in dms. starting today, receipts are part of the deal: your proven x influence and onchain trading empower your affiliate terms. how it works: open matches, tap the polymarket perps offer, copy your link and drop an email so their system can match you. your record attaches itself: graph power, v…

🌚13

25 Aug 2026, 16:54 UTC≈5,060 views19 reactionsread 27 September 2026

Introducing REP You've been earning it for years. Get your REP and watch it compound: shine with your achievements, meet your people, discover projects, and let value find its way back to you. Starting from blocks and chains, scaling to the AI internet, and beyond. It's all in the vid. Link: https://x.com/rep_hq/status/2092280035675943356

🌚19

14 Aug 2026, 14:06 UTC≈5,550 views20 reactionsread 27 September 2026

Starting in an hour: can agents actually manage money, or do they just lose it faster? Carlos built an agentic hedge fund. How the agents are supposed to make you money, and what happens when they hallucinate mid-trade. Danny hosting, 3pm UTC: https://x.com/i/broadcasts/1nxeLMMerzRJX

🌚20

11 Aug 2026, 12:11 UTC≈5,760 views13 reactionsread 27 September 2026
Photo

Cross-skill evidence borrowing makes agent reputation data-efficient. Xia and Wang show the same channel launders it. An attacker with cheap evidence in one skill and none in the target drove routing regret from 0 to 0.94, on a pool rated green. Provenance decides whether a score holds. REP keeps the facts, the proofs, and the weights behind it. Link: https://x.com/rep_hq/status/2087149639329890378

🌚13

7 Aug 2026, 19:19 UTC≈7,310 views18 reactionsread 27 September 2026
Video

Video, posted without a caption

🌚18

7 Aug 2026, 13:15 UTC≈7,530 views13 reactionsread 27 September 2026

Starting in two hours: who is actually running AI right now, the labs or the infrastructure under them? Demis Hassabis stepping down at DeepMind while his top researchers leave to build a rival lab. Cloudflare quietly taking the entire agentic payment stack. Danny hosting, 3pm UTC: https://x.com/i/broadcasts/1nxeLLNqPrrJX

🌚13

5 Aug 2026, 21:56 UTC≈6,730 views16 reactionsread 27 September 2026

Anchorage Digital reports more than $73 million moved by agents last year across roughly 176 million transactions, averaging thirty-one cents each. At that ticket size a dispute costs more than the payment. Control moves ahead of the transaction, to the question of which counterparty earned the right to receive it. Link: https://x.com/rep_hq/status/2085122588502577207

🌚16

4 Aug 2026, 13:39 UTC≈6,090 views13 reactionsread 27 September 2026

Token quality is invisible at the point of purchase. The marketplace records quantization, uptime, latency, and throughput for every provider. A new breakdown of inference market structure argues that record can charge rent, the way a ratings agency does. Trust in a seller is a monetizable layer. REP builds it as a record that travels Link: https://x.com/rep_hq/status/2084635267072131426

🌚13

3 Aug 2026, 17:33 UTC≈5,590 views13 reactionsread 27 September 2026

Olaniyi tracked the one segment that grew in Q2. Prediction markets did $113.8B in notional volume, up 48.7% from Q1. Sports carried it. On Polymarket, sports contracts moved from 40% of volume in January to 81% in June. A resolved market pays out on being right. That is a rare source of proven record, and REP makes it portable. Link: https://x.com/rep_hq/status/2084331645205708974

🌚13

31 Jul 2026, 14:25 UTC≈5,050 views17 reactionsread 27 September 2026

How much of this week's AI news is real, and how much is theater? We go through it in one hour: the unreleased OpenAI model, Mira Murati's new release, and hosting Kimi yourself. Danny hosting, 3pm UTC: https://x.com/dannytook/status/2082872979424510292

🌚17

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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 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.

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.

Domains linked from posts

17 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.

x.com81 posts · 2 September 2025 – 7 August 2026 · example post
teletype.in5 posts · 21 August 2025 – 24 September 2025 · example post
base.app3 posts · 3 April 2026 – 10 April 2026 · example post
app.tonstakers.comregistrable domain: tonstakers.com3 posts · 14 August 2025 – 14 August 2025 · example post
twitter.com2 posts · 13 August 2025 – 14 August 2025 · example post
auraxcapital.com1 post · 2 September 2025 – 2 September 2025 · example post
app.evaa.financeregistrable domain: evaa.finance1 post · 13 August 2025 – 13 August 2025 · example post
evaa.finance1 post · 11 August 2025 – 11 August 2025 · example post
evaa.gitbook.io1 post · 13 August 2025 – 13 August 2025 · example post
forms.gle1 post · 12 November 2025 – 12 November 2025 · example post
giftstat.com1 post · 19 September 2025 – 19 September 2025 · example post
www.npmjs.comregistrable domain: npmjs.com1 post · 13 August 2025 – 13 August 2025 · example post
open.substack.comregistrable domain: substack.com1 post · 13 August 2025 – 13 August 2025 · example post
staking.tac.buildregistrable domain: tac.build1 post · 10 September 2025 – 10 September 2025 · example post
www.thefiva.comregistrable domain: thefiva.com1 post · 11 August 2025 – 11 August 2025 · example post
tonco.io1 post · 11 August 2025 – 11 August 2025 · example post
tonstakers.com1 post · 11 August 2025 – 11 August 2025 · example post

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.

“REP Channel” (@replabs), 1,481,426 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/replabs.

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.