Telegram RegisterThe public register of Telegram
Telegram profile photo for 飞猪bao养 扬帆起航

Channel

飞猪bao养 扬帆起航

@fzby333

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

34subscribers

+9 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-1004490680180
TypeChannel
Username@fzby333
CreatedBetween 1 June 2026 and 11 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/fzby333

Growth

253429.57 August 2026 — 25 subscribers11 August 2026 — 25 subscribers14 August 2026 — 30 subscribers21 August 2026 — 32 subscribers28 August 2026 — 34 subscribers7 August 202628 August 2026
5 measurements spanning 20 days, net +9. 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 24–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 03:0534+2
21 Aug 2026, 07:2832+2
14 Aug 2026, 22:2830+5
11 Aug 2026, 10:0425no change
7 Aug 2026, 15:4725first reading

Engagement

5 posts held, back to 11 August 2026the 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.

ERR · 30 days
2.94%
avg views ÷ 34 subscribers
Avg views / post
1.0
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 5 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 11 August 2026
Posts held5 (11 August 202611 August 2026)
Views total5
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 10:04 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

Video runtime
16s
Average length
5s

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

Recent posts

11 Aug 2026, 10:03 UTC1 viewsread 11 August 2026
Photo

F412 省份:北京 城市:北京 雪生还是工作:学生 学历:本科 年龄: 24 身高: 163 体重:130 罩杯: 大B小c 是否chu:否 能否无套(体检/试纸后) :可 是否可以内S:否 能否口: 否 SM能不能:不能 能否同居:不可 能否过夜:可 能否去其他省份:能 例假日期:月中或月底 有没有纹身:没有 最早出发时间:下月3日 每月陪伴天数:2 每月零花钱:4000 是否有港澳通行证:有 自我评价(加分项):五官端正情绪稳定,活好不粘人, 不能接受金主(雷点):有性疾病或其他传染病 介绍费:7888 xlx 小白兔🐰

11 Aug 2026, 10:03 UTC1 viewsread 11 August 2026
Photo

F411 省份:北京 城市:北京 雪生还是工作:学生 学历:大三 年龄: 21 身高: 162 体重:95 罩杯: C 是否chu: 否 能否无套(体检/试纸后) :否 是否可以内S:否 能否口: 能 SM能不能: 能 能否同居: 否 能否过夜: 能 能否去其他省份: 否 例假日期: 20号左右 有没有纹身: 没有 最早出发时间: 随时 每月陪伴天数: 2 每月零花钱: 6k 是否有港澳通行证:没有 自我评价(加分项): 熊大水多,懂事,配合度高 不能接受金主(雷点): 钱少事多 介绍费:7888 xlx 小白兔🐰

11 Aug 2026, 10:01 UTC1 viewsread 11 August 2026
Photo

豆豆F 省份:北京 城市: 雪生还是工作:实习幼师 学历:大专 年龄:19 身高:168 体重:113 罩杯:C 是否chu:否 体检后能否无t:能无t内 能否口:能 SM能不能:能 能否同居:能 能否过夜:能 能否去其他省份:可以 例假日期:月中 有没有纹身:无 最早出发时间:随时出发 每月陪伴天数:3 每月零花钱:5666 个人优点:清纯可爱长相 绝对反差小母狗 听话乖 巧 嘴甜情商高 温柔 配合度高 性经历很少 不能接受金主:太重口 介绍费7888

Showing the 5 most recent of 5 posts we hold for @fzby333. 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.

Citation-graph rank

Citation-graph rank — 759,573 of 1,629,452 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“飞猪bao养 扬帆起航” (@fzby333), 34 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/fzby333.

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.