Channel
@bigaoa
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
366subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002733815119 |
|---|---|
| Type | Channel |
| Username | @bigaoa |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/bigaoa |
Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 07:56 | 366 | -4 |
| 6 Sept 2026, 05:37 | 370 | -5 |
| 29 Aug 2026, 13:05 | 375 | +2 |
| 22 Aug 2026, 20:34 | 373 | +1 |
| 15 Aug 2026, 01:33 | 372 | +3 |
| 8 Aug 2026, 08:54 | 369 | -1 |
| 8 Aug 2026, 06:20 | 370 | no change |
| 7 Aug 2026, 13:01 | 370 | first reading |
20 posts held, back to 4 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
欢迎新老朋友光临比高 @bigao 人设套图导航区，挑选好三方发编号或者转发给客服 点击下面蓝色文字，可跳转频道进行挑选套图 ⏩亚洲女套图 ⏩亚洲男套图 ⏩欧洲女套图 ⏩欧洲男套图 ⏩女证件套图 ⏩男证件套图 ⏩女私密套图 ⏩定制证件P图 😊比高海外素材 （比高频道导航） 😘😘😘😘😘 @gtabc 😘 感谢您的关注与支持 更多频道请点击 @bigao 进入查看 🔼请鼠标往上面😊移动，挑选您喜欢的套图发编号给客服😊 @gtabc
编号 WN_ #VX637 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 宠物 曝光度低 粉丝4000 922张照片 125个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX638 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 闺蜜照 生日照 宠物 性感照 纹身 浴袍照 床上照 曝光度低 粉丝4000 873张照片 253个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX636 #台湾 保险代理人 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 闺蜜照 生日照 家庭照 比基尼 性感照 诱惑照 1087张照片 239个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX669 #新加坡 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 毕业照 生日照 1364张照片 100个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX670 #新加坡 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 床上照 闺蜜照 宠物 瑜伽 2881张照片 195个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX675 #马来西亚 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 1549张照片 121个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX630 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 高尔夫 生日照 比基尼 性感照 闺蜜照 床上照 345张照片 134个视频 ＿＿需要请联系客服：@gtabc
编号 WN_ #VX629 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 闺蜜照 比基尼 性感照 宠物 曝光度低 粉丝7000 1166张照片 54个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX629 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 生日照 闺蜜照 比基尼 性感照 宠物 曝光度低 粉丝7000 1166张照片 54个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #VX634 #台湾 气质美女 生活场景丰富 自拍多 旅游 美景 美食 时尚会穿搭 闺蜜照 生日照 床上照 宠物 442张照片 69个视频 (带IG）后期可更新＿＿需要请联系客服：@gtabc
编号 WN_ #13XY301 #精品 证件🌕 台湾身份证 #台湾 宝妈 日常 旅游 带娃 自拍 美食 聚会 结婚照 3173张照片视频70个（带ig)＿＿需要请联系客服：@gtabc
Showing the 12 most recent of 20 posts we hold for @bigaoa. 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.
Named by 19 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“亚洲女套图-比高人设包装套图素材” (@bigaoa), 366 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/bigaoa.
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.