Telegram RegisterThe public register of Telegram
Telegram profile photo for 霸哥财团-彩票平台/待遇置顶

Channel

霸哥财团-彩票平台/待遇置顶

@bage2233

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

6,880subscribers

+1,199 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002016709252
TypeChannel
Username@bage2233
Description#彩票平台 #彩票娱乐 #时时彩平台 #分分彩平台 霸哥财团 霸哥财团 15年信誉为您保驾护航 玩彩就选霸哥财团 霸哥财团 15年信誉为您保驾护航 玩彩就选霸哥财团 霸哥财团霸哥: @bage 霸哥财团专线: @bage2 霸哥财团专线: @bage5 霸哥财团雄霸: @ffcc7 霸哥平台网址: @bage77bot 平台名+地址 霸哥双向机器人 @bage699bot 霸哥平台注册: @bage8989 合作项目列表: @bage888
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/bage2233

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@bage2233/555 · this entry9 Jul 2026, 10:27 UTC@bage888/60913 Jul 2026, 11:52 UTC1.004 days
@bage888/6223 Aug 2026, 07:36 UTC@bage2233/568 · this entry3 Aug 2026, 07:37 UTC1.00under a minute
@bage888/6233 Aug 2026, 10:02 UTC@bage2233/569 · this entry3 Aug 2026, 10:02 UTC1.00under a minute
@bage888/6359 Aug 2026, 16:03 UTC@bage2233/581 · this entry22 Aug 2026, 10:10 UTC1.0013 days
@bage888/64724 Aug 2026, 13:31 UTC@bage2233/584 · this entry24 Aug 2026, 15:15 UTC1.001.7 hours
@bage2233/588 · this entry3 Nov 2026, 10:42 UTC@bage888/6553 Nov 2026, 10:42 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@bage8889 (8/8 hand-verifiable sample passed)0.99under a minute@bage888 (6–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 4 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 16 comparable posts for this entry, running 9 July 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @bage2233 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,6816,8806,280.57 August 2026 — 5,681 subscribers7 August 2026 — 5,681 subscribers7 August 2026 — 5,706 subscribers10 August 2026 — 5,782 subscribers13 August 2026 — 5,823 subscribers16 August 2026 — 5,909 subscribers19 August 2026 — 5,980 subscribers23 August 2026 — 6,098 subscribers25 August 2026 — 6,094 subscribers29 August 2026 — 6,150 subscribers1 September 2026 — 6,193 subscribers5 September 2026 — 6,293 subscribers10 September 2026 — 6,400 subscribers14 September 2026 — 6,434 subscribers18 September 2026 — 6,420 subscribers28 September 2026 — 6,495 subscribers5 October 2026 — 6,638 subscribers12 October 2026 — 6,770 subscribers15 October 2026 — 6,763 subscribers18 October 2026 — 6,770 subscribers21 October 2026 — 6,791 subscribers24 October 2026 — 6,774 subscribers27 October 2026 — 6,795 subscribers29 October 2026 — 6,834 subscribers1 November 2026 — 6,827 subscribers4 November 2026 — 6,834 subscribers7 November 2026 — 6,861 subscribers10 November 2026 — 6,828 subscribers15 November 2026 — 6,880 subscribers7 August 202615 November 2026
29 measurements spanning 100 days, net +1,199. 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 5,501–7,060 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
15 Nov 2026, 09:426,880+52
10 Nov 2026, 07:406,828-33
7 Nov 2026, 01:206,861+27
4 Nov 2026, 09:456,834+7
1 Nov 2026, 15:196,827-7
29 Oct 2026, 18:486,834+39
27 Oct 2026, 00:166,795+21
24 Oct 2026, 07:466,774-17
21 Oct 2026, 03:076,791+21
18 Oct 2026, 01:386,770+7
15 Oct 2026, 09:066,763-7
12 Oct 2026, 01:596,770+132
5 Oct 2026, 21:356,638+143
28 Sept 2026, 21:206,495+75
18 Sept 2026, 22:186,420-14
14 Sept 2026, 09:396,434+34
10 Sept 2026, 23:426,400+107
5 Sept 2026, 16:366,293+100
1 Sept 2026, 08:456,193+43
29 Aug 2026, 06:166,150first reading

Engagement

18 posts held, back to 9 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 24 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.60%
avg views ÷ 6,880 subscribers
Avg views / post
179
4 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
of 18 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 13 November 2026
Posts held18 (9 July 2026 – 13 November 2026)
Views total716
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 09:37 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
449
Videos
6
Links
275

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

Reaction mix

7 reactions across 7 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤7100.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 8 of the 18 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 9 July 2026 to 13 November 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

Telegram’s own ‘edited’ marker: 1 of 4 posts held from the last 30 days (25.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Nov 2026, 06:40 UTC92 viewsread 16 November 2026
Photo

《鼎上》已放号, 公测不删档16号开业。 ⭐️团队开业扶持活动经营中,月分红/高占成 双模式待遇,团队带量详谈具体待遇。 ⭐️公测期间13 - 15 号期间可以用正式账号联系客服开带测试分的公测账号 ⭐️正式开业 - 开放充提时间: 11月16号 09:00 鼎上初始密码 ds123456 https://888.dsyule03.com https://888.dsyule05.com https://888.dsyule10.com https://888.dsyule25.com https://666.dsyule1170.com https://666.dsyule2320.com https://666.dsyule3627.com https://666.dsyule3780.com https://dsdir.dsyule21.com https://dsdir.dsyule32.com #原生…

9 Nov 2026, 10:29 UTC148 viewsread 16 November 2026

🤖表情包机器人: @biaoqinggebot 霸哥表情包频道: @bage557

4 Nov 2026, 13:11 UTC265 viewsread 16 November 2026
Photo

欧亿10 《鼎上娱乐》待遇已公布 鼎上娱乐 账号创号时间 11月13号 09:00 ,( 需要预留发财账户的可以预留了 )需公测账号的用户,使用正式账号登录后联系客服即可创建带测试分的公测账号进行游戏公测试玩 公测时间 : 13号 - 15 号 正式开业 - 开放充提时间: 11月16号 09:00 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地址 😘霸哥双向机器人 @bage699bot 😘霸哥平台注册: @bage8989 😘合作项目列表: @bage888 👉点击查看·霸哥财团集团近期合作项目👈 👉点击返回·集团合作目录👈

3 Nov 2026, 10:42 UTC211 viewsread 16 November 2026
Photo

欧亿10 《鼎上娱乐》待遇已公布 鼎上娱乐 账号创号时间 11月13号 09:00 ,( 需要预留发财账户的可以预留了 )需公测账号的用户,使用正式账号登录后联系客服即可创建带测试分的公测账号进行游戏公测试玩 公测时间 : 13号 - 15 号 正式开业 - 开放充提时间: 11月16号 09:00 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地址 😘霸哥双向机器人 @bage699bot 😘霸哥平台注册: @bage8989 😘合作项目列表: @bage888 👉点击查看·霸哥财团集团近期合作项目👈 👉点击返回·集团合作目录👈

24 Aug 2026, 15:15 UTC705 views1 reactionsread 16 November 2026
Photo

《欧亿10 ·鼎上娱乐》即将上线。 开业时间 : 2026年10月16号 👉鼎上 logo+海报宣传资料 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地址 😘霸哥双向机器人 @bage699bot 😘霸哥平台注册: @bage8989 😘合作项目列表: @bage888 👉点击查看·霸哥财团集团近期合作项目👈 👉点击返回·集团合作目录👈

❤1

22 Aug 2026, 10:10 UTC554 views1 reactionsread 16 November 2026
Photo

《✯ 泰 达 ✯ ➤ 国內线路: https://666.tdyule8444.com https://666.tdyule4141.com https://666.tdyule9289.com https://666.tdyule6443.com https://666.tdyule5451.com ➤ 海外线路: https://888.tdyule62.com https://888.tdyule19.com https://888.tdyule06.com https://888.tdyule66.com https://888.tdyule49.com ➤ 专用线路: https://tddir.tdyule55.com https://tddir.tdyule20.com ➤ APP下载链结 【安卓/苹果通用】 https://d19dl1m2i2wmm.cloudfront.net/8k86cc 【苹果-P…

❤1

14 Aug 2026, 06:53 UTC413 views1 reactionsread 16 November 2026
Photo

Vs2哈希 无分红线路待遇 Vs2易记域名:默认密码V88888 vs2.vip 域名 1 https://www.vs2vip1.com IP 域名 https://137.220.134.150:8888 长域名 https://web-vs2-01.trafficmanager.net 备用域名 2 https://www.vs2vip1.com 备用域名 3 https://www.vs2vip3.com 长域名 2 https://web-vs2-02.trafficmanager.net 官方频道 https://t.me/veryspe 投注机器人 @vs2hb_bot 播报机器人 @vs2bb_bot 建议优先记住 vs2.vip,其他域名作为备用线路保存。 Vs2注册链接:邀请码1497r7 注册地址 注册地址 注册地址 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥…

❤1

13 Aug 2026, 04:53 UTC295 viewsread 16 November 2026
Photo

Vs2哈希 无分红线路待遇 1:彩票/哈希待遇 1940 实时工资2.8% 彩票日结工资 (无保底) 第一档:彩票日结工资比例:最低 有效6人60万有效投注-0.05% 第二档:彩票日结工资比例:最低 有效12人120万有效投注-0.1% 投注1000人民币为一个有效人数(或其他等价外币) 有效统计区块链游戏,销量和有效人数货币单位人民币,或其他等价外币 (特别提醒:有效按照 C U T 分别计算,如果有一个人 投注了 500CNY。100U 不算为有效 ) 2:三方待遇 电子,百家乐,1%。 体育0.6% 3:占成规则:可占成自身线路10%(彩票游戏后哈希游戏) 😘 北京时间8/13 15:00开户 正式开业 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地址…

9 Aug 2026, 10:25 UTC372 views1 reactionsread 12 November 2026
Photo

vs2代理待遇 区块链:1940+2.8%实时+0.1%日结(无保底) 占成10% 三方:电子百家乐1% 体育0.6% 8月13号3点开户,满待遇➕私 8月15号开业 VS2公测删档注册链接:https://www.vs2vip1.com:8888/register?line=7bb51f6610e51240419dc2c996a69d33&invite_code=3u3560 欢迎大家找bug:重大bug会安排红包的 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地址 😘霸哥双向机器人 @bage699bot 😘霸哥平台注册: @bage8989 😘合作项目列表: @bage888 👉点击查看·霸哥财团集团近期合作项目👈 👉点击返回·集团合作目录👈

❤1

7 Aug 2026, 07:49 UTC357 viewsread 12 November 2026
Photo

《✯ 泰 达 ✯ ➤ 国內线路: https://666.tdyule8444.com https://666.tdyule4141.com https://666.tdyule9289.com https://666.tdyule6443.com https://666.tdyule5451.com ➤ 海外线路: https://888.tdyule62.com https://888.tdyule19.com https://888.tdyule06.com https://888.tdyule66.com https://888.tdyule49.com ➤ 专用线路: https://tddir.tdyule55.com https://tddir.tdyule20.com ➤ APP下载链结 【安卓/苹果通用】 https://d19dl1m2i2wmm.cloudfront.net/8k86cc 【苹果-P…

5 Aug 2026, 19:19 UTC278 viewsread 4 November 2026
Photo

Vs无分红线路待遇 1:彩票/哈希待遇 1940 实时工资2.8% 彩票日结工资 (无保底) 第一档:彩票日结工资比例:最低 有效6人60万有效投注-0.05% 第二档:彩票日结工资比例:最低 有效12人120万有效投注-0.1% 投注1000人民币为一个有效人数(或其他等价外币) 有效统计区块链游戏,销量和有效人数货币单位人民币,或其他等价外币 (特别提醒:有效按照 C U T 分别计算,如果有一个人 投注了 500CNY。100U 不算为有效 ) 2:三方待遇 电子,百家乐,1%。 体育0.6% 3:占成规则:可占成自身线路10%(彩票游戏后哈希游戏) 😘开放注册:2026/8/13 😘 正式开业:2026/8/15 😘霸哥财团霸哥: @bage 😘霸哥财团专线: @bage2 😘霸哥财团专线: @bage5 😘霸哥财团雄霸: @ffcc7 😘霸哥平台网址: @bage77bot 平台名+地…

3 Aug 2026, 10:02 UTC616 views0 reactionsread 4 November 2026
Photo

《✯ 泰 达 ✯ ➤ 国內线路: https://666.tdyule8444.com https://666.tdyule4141.com https://666.tdyule9289.com https://666.tdyule6443.com https://666.tdyule5451.com ➤ 海外线路: https://888.tdyule62.com https://888.tdyule19.com https://888.tdyule06.com https://888.tdyule66.com https://888.tdyule49.com ➤ 专用线路: https://tddir.tdyule55.com https://tddir.tdyule20.com ➤ APP下载链结 【安卓/苹果通用】 https://d19dl1m2i2wmm.cloudfront.net/8k86cc 【苹果-P…

Showing the 12 most recent of 18 posts we hold for @bage2233. 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 1 registered channel — 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

博彩社区-平台爆光
@bocaishen8 · 89,212
Telegram ranks this channel #55 of 71 here — alongside 70 others — read 22 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“霸哥财团-彩票平台/待遇置顶” (@bage2233), 6,880 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/bage2233.

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.