Channel
@txjs999
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
134subscribers
-90 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003349414791 |
|---|---|
| Type | Channel |
| Username | @txjs999 |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/txjs999 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 05:54 | 134 | -24 |
| 23 Aug 2026, 17:33 | 158 | -39 |
| 15 Aug 2026, 17:43 | 197 | -22 |
| 8 Aug 2026, 10:35 | 219 | no change |
| 8 Aug 2026, 08:56 | 219 | -5 |
| 7 Aug 2026, 20:02 | 224 | first reading |
4 posts held, back to 8 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 4 (8 August 2026 – 8 August 2026) |
| Views total | 4 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:35 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.
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.
编号：2608081092 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 月2512 所在省份：江苏 所在城市：常州市金坛市 年龄:19 身高:168 体重:110 罩杯:80D 当前职业：博主 是否chu女:否 是否有纹身/抽烟：无 能否接受sm（轻中重度）:中 能否接受口:能 能否接受体检后无tao :能 能否接受体检后内se ：否 能否同居:能 能否过夜:能 每月可连续陪伴的天数: 3 短期三天生活费多少：7k 生活费分几次付（2-4次）:2 能否去其他城市:能 能否去港/澳:能 自我加分项：身材好有肉的地方包满意 情绪价值拉满 最快见面时间:最近 姨妈日期：20-7 雷点（不能接受的）：目前没有 介绍费：7888 kiki-yx 888RMB入会，单单享折扣 #江苏包养 #南京包养 #苏州包养 ❤️甜心包养 专注江苏包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 …
编号：2608081081 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 省份；安徽 江苏a737 城市；芜湖 南京 年龄：19 身高：168 体重：53 🐻杯: a 职业：雪生 能否飞外地：可 能否过夜/同居：可 是否抽烟/纹身: 否 能否kou：可 能否体检后不d/🐍: 否 预期费用：1.5w 每🈷️可陪天数: 3天1.5w 能否接受sm : 轻微 是否chu女: 否 可分几次付：2 姨妈时间：月底 是否可去港澳；没证 自我加分项：06女大新脸 纯欲可甜可盐 事少脾气好能喝能玩会唱歌 雷点（不接受）: 介绍费：7888鱼鱼 888RMB入会，单单享折扣 #江苏包养 #南京包养 #苏州包养 ❤️甜心包养 专注江苏包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot 🏆入会联系客服看视频认证
编号：2608081078 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 省份:江苏 城市:苏州 年龄:21 身高:165 体重:115 罩杯:C 职业: 是否chu女:否 能否接受口:是 能否接受SM:否 能否接受无套(双方体检或测试纸后):🉑 是否接受内🐍:否 可否同居:否 可否过夜:是 是否抽烟或纹身:一点 大姨妈日期:18号 可否飞往外地:是 月可陪伴天数:7 最快多久出发:随时 是否有港澳通行证:是 生活费要多少：1天2k 3天6k 生活费分几次：2-4 自我加分项：听话懂事会配合 无毛 🐻大💦多 雷点：不爱干净 介绍费：7888 温予安l 888RMB入会，单单享折扣 #江苏包养 #南京包养 #苏州包养 ❤️甜心包养 专注江苏包养 包养须知➡️➡️ @txxr888 ❤️甜心客服 @baomei888 🤖双向机器人 @tianxinbaoyang_bot 🏆入会联系客服看视频认证
编号：2608081066 (点击复制) 🔍 点击查看验证视频 ⭐ 点击收藏该资源 ⭐ 省份： 江苏 城市： 徐州（7月份起在长沙工作） 年龄： 22 身高： 165 体重：54kg 罩杯： C 雪生/工作： 刚毕业 纹身抽烟： 没有纹身 偶尔抽烟 雷点（不能接受）： 素质差，不卫生 是否chu女: 否 能否接受SM： 轻微 金主体检后无套（不内🐍）：否 能否接受口： 🉑 可同居： 否 可过夜： 否 可陪伴天数： 3天，7天 可否飞往外省： 🉑 可否chu国：否 宝宝要多少生活费：1w，2w 支付费用可否2次付完：2 对金主的要求：干净清爽 姨妈期时间：10号左右 匹配好几天出发找男友：随时 自我加分项：乖巧听话 懂事不黏人 会说话做事 酒量还可以可以陪伴应酬 能够提供情绪价值 介绍费：6888 xw 小白兔🐰 888RMB入会，单单享折扣 #江苏包养 #南京包养 #苏州包养 ❤️甜心包养 专注江苏包养 包养须知➡️➡️ …
Showing the 4 most recent of 4 posts we hold for @txjs999. 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 — 343,923 of 1,627,068entries 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“江苏包养｜甜心包养江苏频道” (@txjs999), 134 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/txjs999.
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.