Telegram RegisterThe public register of Telegram
Telegram profile photo for SY租号铺【唯一频道】

Channel

SY租号铺【唯一频道】

@SY3650

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

10,248subscribers

-16,780 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002957133286
TypeChannel
Username@SY3650
Description售后联系客服 @BQ6663
Created30 September 2025 — measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live18 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 18 November 2026
On Telegramt.me/SY3650

Topic

Gaming — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

10,24828,26919,258.58 August 202618 November 2026
65 measurements spanning 102 days, net -16,780. 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 7,545–30,972 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
18 Nov 2026, 09:0410,248-177
15 Nov 2026, 08:0610,425-466
12 Nov 2026, 01:0110,891-100
10 Nov 2026, 00:1810,991-50
8 Nov 2026, 14:2011,041-37
7 Nov 2026, 07:4011,078-28
6 Nov 2026, 10:2011,106-26
5 Nov 2026, 10:2911,132-11
4 Nov 2026, 08:0911,143-31
3 Nov 2026, 09:5111,174-8
2 Nov 2026, 13:1611,182-14
1 Nov 2026, 16:0711,196-64
31 Oct 2026, 18:3911,260-164
30 Oct 2026, 15:1611,424-319
29 Oct 2026, 12:5511,743-76
28 Oct 2026, 14:0811,819-68
27 Oct 2026, 17:1111,887-180
26 Oct 2026, 14:5412,067-116
25 Oct 2026, 16:4012,183-1
24 Oct 2026, 13:4612,184first reading

Engagement

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

ERR · 30 days
7.97%
avg views ÷ 10,248 subscribers
Avg views / post
817
49 posts measured
Reaction rate
3.74%
reactions ÷ views · ER floor
Posts in window
49
of 194 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 18 November 2026
Posts held194 (30 September 2025 – 18 November 2026)
Views total40,042
Reactions total1,498
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 13:12 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
6
Videos
1
Links
5

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

Video runtime
1m 11s
Average length
1m 11s

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

3,374 reactions across 188 posts, in 22 distinct kinds. The most used accounts for 81.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2,76081.8%
❤36310.8%
🤣501.48%
👎270.8%
🤔270.8%
🤮270.8%
🙏210.622%
👏140.415%
😁140.415%
🔥130.385%
🤨100.296%
🤬90.267%
🖕70.207%
😭60.178%
🥰60.178%
💩50.148%
😡50.148%
😢40.119%
🍾30.089%
🌭10.03%
2 further kinds20.059%

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

Measured over the 194 most recent posts we hold, published 30 September 2025 to 18 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: 7 of 49 posts held from the last 30 days (14.3%) 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).

17 Nov 2026, 05:56 UTC481 views13 reactionsread 19 November 2026

皮肤号,地铁号,等级号,段位号库存加了 跑刀量大的联系我,稳定跑刀基本无顶号

👍12🤔1

16 Nov 2026, 03:37 UTC297 views12 reactionsread 16 November 2026

支付不了的等几分钟再试试

👍10❤1🤔1

15 Nov 2026, 03:32 UTC914 views34 reactionsread 19 November 2026

✅售后已全部处理完毕! 📢如有遗漏或问题尚未解决,请及时联系客服处理! 🫰售后服务一直都在,持续为您的账号保驾护航! ✈️TG售后客服:@BQ6663 🛒下单地址: https://www.luoyew.net/shop/SY3650

👍32❤2

14 Nov 2026, 08:13 UTC≈1,100 views53 reactionsread 19 November 2026

库存加了,无敌质量 有跑刀的dd,都是回归号,基本没顶号问题

👍53

14 Nov 2026, 03:53 UTC≈1,140 views49 reactionsread 19 November 2026

客服一直在,兄弟们放心下单即可 @BQ6663

👍46❤1🔥1🤔1

13 Nov 2026, 14:20 UTC≈1,200 views58 reactionsread 19 November 2026

地铁号,皮肤号库存加了

👍57❤1

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

Posts edited after publishing

@SY3650 edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
21 August 2026
Most recent edit
14 November 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @SY3650 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
14 August 2026
Most recent seen missing
15 August 2026
Median time before seen missing
19 hours
Seen missing in the last 30 days
0

Polls

The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

17 Aug 2026, 06:28 UTCAnonymous Poll333 voters

晚上9点要不要加200个福利号

  1. 要92%
  2. 不要8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

14 Aug 2026, 04:49 UTCAnonymous Poll373 voters

晚上9点还上架免费授权吗

  1. 不用21%
  2. 用79%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

13 Aug 2026, 07:37 UTCAnonymous Poll375 voters

晚上9点还加免费授权号吗

  1. 加93%
  2. 不加7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 194 most recent posts we hold, published 30 September 2025 to 18 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

Named by

Channels on the register whose posts name this channel's handle.

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

“SY租号铺【唯一频道】” (@SY3650), 10,248 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/SY3650.

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.