Telegram RegisterThe public register of Telegram
Telegram profile photo for 佳佳

Channel

佳佳

@su23548

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

699subscribers

-276 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-1003756650159
TypeChannel
Username@su23548
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/su23548

Topic

Giveaways & airdrops — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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

680975827.57 August 2026 — 975 subscribers8 August 2026 — 975 subscribers8 August 2026 — 972 subscribers15 August 2026 — 899 subscribers23 August 2026 — 706 subscribers29 August 2026 — 680 subscribers6 September 2026 — 716 subscribers15 September 2026 — 699 subscribers6997 August 202615 September 2026
8 measurements spanning 39 days, net -276. 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 636–1,019 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 06:01699-17
6 Sept 2026, 22:18716+36
29 Aug 2026, 23:08680-26
23 Aug 2026, 07:16706-193
15 Aug 2026, 12:03899-73
8 Aug 2026, 06:42972-3
8 Aug 2026, 00:46975no change
7 Aug 2026, 16:18975first reading

Engagement

20 posts held, back to 5 August 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10s
Average length
5s

Measured directly from 2 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 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 1 reactions 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 August 2026 to 7 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

7 Aug 2026, 09:37 UTC241 viewsread 8 August 2026
Photo

💐💐💐开奖了💐💐💐 【骑士团☆佳佳 半价活动】开奖了 本期总参与人数:287 少女币加成数:14 1、林云(欧皇版)(消息数32 加成数0)获得:半价p 2、何春秋(消息数22 加成数0)获得:p-100 3、abao666(消息数22 加成数0)获得:pp-200 4、蜡笔没了(消息数34 加成数2)获得:夜-300 兑奖请联系 @su235489 谨祝中奖用户大吉大利万事如意 更多资讯请关注

7 Aug 2026, 07:49 UTC252 viewsread 8 August 2026
Photo

💐💐💐开奖了💐💐💐 【府上佳佳半价 抽奖活动】开奖了 本期总参与人数:367 嫩妹币加成数:4 1、万金油(消息数20 加成数0)获得:半价/p 2、闭眼深呼吸(消息数22 加成数0)获得:p减100 3、何春秋(消息数29 加成数0)获得:pp减200 4、排雷跑断腿(消息数61 加成数0)获得:包夜减300 5、轻笑(消息数28 加成数0)获得:包夜减300 6、旧巷老友(消息数22 加成数0)获得:包夜减300 兑奖请联系 @su235489 谨祝中奖用户大吉大利万事如意 更多资讯请关注

7 Aug 2026, 07:42 UTC236 viewsread 8 August 2026
Photo

🎉💐🎉Winner Winner🎉💐🎉 @su235489 佳佳杰尼龟福利抽奖活动 1. 兑奖请联系 @su235489 2. 优惠券自开奖时间起 7 天内有效。 3. 炸号者中奖作废。 4. 发奖人在发奖前请仔细阅读发奖指引,以防奖品被冒领造成不必要的损失👉 https://t.me/kind216/238 🎫参与人数: 344|号码总数: 344 🔖中奖名单如下: 1- 墨曈[+0] 🉐: 包夜优惠300 2- 阿达西[+0] 🉐: p优惠100 3- 原乡六郎[+0] 🉐: p半价 4- 叽叽波[+0] 🉐: pp优惠200 5- 木子在启航🔥🔥[+0] 🉐: 包夜优惠300

6 Aug 2026, 17:10 UTC334 viewsread 8 August 2026

一后凡是遇到偷钱的直接报j我发现现在偷钱的越来越多了

6 Aug 2026, 14:13 UTC427 viewsread 8 August 2026

【广州茶馆】:https://t.me/gzcg9 【时间】:2026-08-04 【老师】:佳佳 【账号】:@su235489 【留名】:T4T44 【颜值】:如频道 【身材】:如频道 【罩杯】:感觉b+到C 【服务】:8 【态度】:8 【位置】:海珠 【评分】:8 【过程】:中了佳佳老师的半价,果断约,地铁上盖,方便。颜值身材见频道,服务如课表。口可以,女上也卖力。值得一提是🐻很有手感,女上时很爽。姿势配合,换了2,3个姿势,顺利出货。

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

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

“佳佳” (@su23548), 699 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/su23548.

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.