Telegram RegisterThe public register of Telegram
Telegram profile photo for 帆室邻

Channel

帆室邻

@FanKetchup

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,589subscribers

+27 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001207765290
TypeChannel
Username@FanKetchup
Created26 September 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live9 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/FanKetchup

Growth

2,5592,5892,5746 August 2026 — 2,562 subscribers6 August 2026 — 2,562 subscribers9 August 2026 — 2,560 subscribers12 August 2026 — 2,559 subscribers16 August 2026 — 2,560 subscribers19 August 2026 — 2,566 subscribers22 August 2026 — 2,574 subscribers28 August 2026 — 2,577 subscribers31 August 2026 — 2,584 subscribers3 September 2026 — 2,588 subscribers9 September 2026 — 2,589 subscribers6 August 20269 September 2026
11 measurements spanning 34 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 2,555–2,594 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 14:172,589+1
3 Sept 2026, 23:212,588+4
31 Aug 2026, 04:542,584+7
28 Aug 2026, 01:132,577+3
22 Aug 2026, 15:442,574+8
19 Aug 2026, 13:562,566+6
16 Aug 2026, 05:162,560+1
12 Aug 2026, 18:462,559-1
9 Aug 2026, 15:312,560-2
6 Aug 2026, 05:312,562no change
6 Aug 2026, 05:292,562first reading

Engagement

21 posts held, back to 17 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 21 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10s
Average length
10s

Measured directly from 1 video 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

463 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 55.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🌭25555.1%
🍌20844.9%

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

Measured over the 21 most recent posts we hold, published 17 May 2026 to 6 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

6 Aug 2026, 15:28 UTC374 views18 reactionsread 7 August 2026
Video

玩了一晚上黄油 有点年头的那种

🍌17🌭1

30 Jul 2026, 04:53 UTC≈1,700 views21 reactionsread 7 August 2026

既然往群里转发内容 相当于往群里搬屎 那给群添加聊天机器人 岂不相当于往群里搬了个屁眼

🌭17🍌4

26 Jul 2026, 09:24 UTC≈1,230 views8 reactionsread 7 August 2026
Photo

以节奏天国对延迟的敏感程度 不仅防盗版,还防电视玩家

🍌6🌭2

22 Jul 2026, 23:52 UTC≈1,410 views20 reactionsread 7 August 2026

第一次因为思维短路而惊醒 起因是梦里有人说了这句话: 世界上不存在概率为零的事情 除了 “世界上不存在概率为零的事情” 这个事情 然后我就在思维风暴中惊醒了!

🍌17🌭3

15 Jul 2026, 16:25 UTC≈1,760 views61 reactionsread 7 August 2026

换了老板 换了同事 结果他们对我 都有个同样的第一印象 “你好白啊”

🌭43🍌18

9 Jul 2026, 01:46 UTC≈2,060 views14 reactionsread 7 August 2026
Photo

A\真奇怪 一边针对中文用户做一大堆限制 一边发布含一堆中文例子的论文 https://transformer-circuits.pub/2026/workspace/index.html

🍌11🌭3

1 Jul 2026, 16:12 UTC≈2,150 views42 reactionsread 7 August 2026

谁还记得6年前 有个受到邀请才能加入的 👋clubhouse语音社交软件啊

🌭33🍌9

20 Jun 2026, 09:33 UTC≈2,530 views28 reactionsread 7 August 2026
Photo

路过家洗衣房 人多的时候 那种啪嗒啪嗒的声音 真的很像洗衣机甩干

🌭18🍌10

19 Jun 2026, 12:13 UTC≈2,250 views27 reactionsread 7 August 2026
Sticker

Sticker, posted without a caption

🌭21🍌6

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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.

简中互联网废物大赏
@fucku_idiot · 40,137
Telegram ranks this channel #28 of 47 here — alongside 46 others — read 30 August 2026
每日消费电子观察
@CE_Observe · 74,327
Telegram ranks this channel #38 of 62 here — alongside 61 others — read 19 August 2026
平壤卫视
@pingrangTV · 29,107
Telegram ranks this channel #39 of 45 here — alongside 44 others — read 8 September 2026
Solidot
@solidot · 44,631
Telegram ranks this channel #44 of 59 here — alongside 58 others — read 28 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists 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 9 September 2026 — this entry's latest reading, not the date you are reading this.

“帆室邻” (@FanKetchup), 2,589 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/FanKetchup.

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.