Telegram RegisterThe public register of Telegram
Telegram profile photo for 同城附近人交友👩‍❤️‍👨

Channel

同城附近人交友👩‍❤️‍👨

@xxp48

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

33,730subscribers

-2,513 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002153617122
TypeChannel
Username@xxp48
Description一个致力于同城交友信息、同城需求的频道。投稿联系机器人: https://t.me/tcj188_bot
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/xxp48

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 5 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qglf1/28923130 Aug 2026, 13:21 UTC@xxp48/682937 · this entry30 Aug 2026, 13:23 UTC1.002 minutes
@qglf1/3311971 Oct 2026, 14:17 UTC@xxp48/724879 · this entry1 Oct 2026, 14:21 UTC1.004 minutes
@qglf1/34416711 Oct 2026, 17:19 UTC@xxp48/737850 · this entry11 Oct 2026, 17:19 UTC1.00under a minute
@qglf1/35916422 Oct 2026, 15:13 UTC@xxp48/752861 · this entry22 Oct 2026, 15:16 UTC1.004 minutes
@qglf1/36639728 Oct 2026, 14:00 UTC@xxp48/760071 · this entry28 Oct 2026, 14:12 UTC1.0012 minutes
@qglf1/3711081 Nov 2026, 15:09 UTC@xxp48/764771 · this entry1 Nov 2026, 15:09 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@qglf1477 (8/8 hand-verifiable sample passed)0.994 minutes@qglf1 (447–30)
@tgt11614 (8/8 hand-verifiable sample passed)1.00under a minute@tgt116 (9–5)
@guangzhou98310 (8/8 hand-verifiable sample passed)1.00under a minute@guangzhou983 (7–3)
@shanghaishh7 (7/7 hand-verifiable sample passed)1.0072 seconds@shanghaishh (4–3)
@xgg137 (7/7 hand-verifiable sample passed)0.975 daysthis entry (4–3)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 470 of the 470 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 1,201 comparable posts for this entry, running 7 August 2026 to 14 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @shanghaishh. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 15 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

33,73036,24334,986.57 August 202612 November 2026
65 measurements spanning 97 days, net -2,513. 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 33,353–36,620 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
12 Nov 2026, 19:4633,730-35
10 Nov 2026, 17:5033,765-32
9 Nov 2026, 07:5833,797-52
7 Nov 2026, 22:2233,849-25
6 Nov 2026, 20:2833,874-19
5 Nov 2026, 17:2433,893-27
4 Nov 2026, 19:5133,920-28
3 Nov 2026, 21:2633,948-12
2 Nov 2026, 20:1133,960-13
1 Nov 2026, 23:3433,973-12
1 Nov 2026, 02:4933,985-29
31 Oct 2026, 03:3934,014-33
30 Oct 2026, 06:3434,047-36
29 Oct 2026, 08:5634,083-34
28 Oct 2026, 04:5134,117-22
27 Oct 2026, 04:3034,139-35
26 Oct 2026, 05:5134,174-23
25 Oct 2026, 07:0534,197-33
24 Oct 2026, 07:1434,230-19
23 Oct 2026, 10:3734,249first reading

Engagement

1,244 posts held, back to 7 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 186 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.053%
avg views ÷ 33,730 subscribers
Avg views / post
17.7
421 posts measured
Reaction rate
5.95%
reactions ÷ views · ER floor
Posts in window
421
of 1,244 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. It is computed over the 56 of 421 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held1,244 (7 August 2026 – 15 November 2026)
Views total7,462
Reactions total71
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 06: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.

What this channel posts

Photos
≈447,000
Videos
≈7,850
Links
≈9,420

Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
15m 32s
Average length
9s

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

Reaction mix

145 reactions across 119 posts, in 7 distinct kinds. The most used accounts for 86.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12586.2%
❤74.83%
👏32.07%
💯32.07%
🔥32.07%
🎉21.38%
👀21.38%

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

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 August 2026 to 15 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: 0 of 421 posts held from the last 30 days (0%) 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).

15 Nov 2026, 06:29 UTC1 views0 reactionsread 15 November 2026
Photo

#开封 #个人兼职 #已验证放心CJ 郑州 商丘 周口 南阳 许昌 新乡 漯河 洛阳 河南全区00后新人 干净整洁身体健康 无体味贴心服务 高适配度待客如男友情绪价值到位 希望为一位哥哥都有一个满意的体验 上课600p热情服务前戏调情 花式吹箫舌尖滑蛋 激情啪啪 窃窃私语 帝王之路:情趣黑丝双龙戏珠过皮吸水冰火 深唯 观音坐莲熊推臀腿滑 听话乖巧多紧嫩 期待您的调教 禁醉酒嗑药 菊 照片课表 @nianqi668 客服 @zhiguang67 双向客服 @zhiguang79bot 选妃交流群 @zhiguang883 联系 qq3781293441

15 Nov 2026, 04:28 UTC17 viewsread 15 November 2026
Photo

#重庆 #个人兼职 #可上门 • 𝐇𝐞𝐢𝐠𝐡𝐭身高/168 • 𝐖𝐞𝐢𝐠𝐡𝐭体重/95 • 𝐁𝐮𝐬𝐭胸围/真实C(天然🐻超软) • 𝐎𝐜𝐜𝐮𝐩𝐚𝐭𝐢𝐨𝐧职业/ 平面/淘宝模特 ⭐️高颜女友系⭐️ 身穿大牌 性感洋气 双商高 听话 120cm细长腿 皮肤白皙 零风尘感 ✨ *气质御姐 自然精致 纯欲性感 ✨ 🉑69 🐍💋 双飞 飞机: @uulove1 双向机器人: @uuloveoobot 个人频道 @UUlove7 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:28 UTC11 viewsread 15 November 2026
Photo

#天津 #个人兼职 #可上门 💗🉑🐍吻🉑69🉑🚗镇 💗不催不事 💗性格文静 乖巧听话 积极配合 ❤️高素质 贴心 女友feel 好评如潮 飞机: @yuyulo1 双向机器人: @yuyubabybot 个人频道 @yuyuoo9 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:28 UTC6 viewsread 15 November 2026
Photo

#上海 #个人兼职 #可上门 年龄/𝑎𝑔𝑒: 05 身高/ℎ𝑡:168cm 罩杯/𝑐𝑢𝑝:C 体重/𝑤𝑡: 45k 🎀皮肤雪白光滑 BB超紧 三点粉💗 🎀敏感体质易湿会吸娇喘 外纯内骚 🙈易抽搐 高潮爱叫“爸爸" 🎀主动配合度100%自动摇摇机 榨汁机 🍹 🎀性格超好 温柔高素质 双商高 🎀爱好:画画 🎨跳舞💃无不良嗜好 🎀小女朋友约会感觉 飞机: @yuyulo1 双向机器人: @yuyubabybot 个人频道 @yuyuoo9 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:27 UTC5 viewsread 15 November 2026
Photo

#北京 #个人兼职 #可上门 168cm/ 47kg/🐻C 偶尔兼职 百变风格 0整容 性格超好 🛏上功夫极棒 可纯可欲 气质不凡 懂点小浪漫💕的干净温柔女孩 可🐍纹69 海底捞般的服务 飞机: @yuyulo1 双向机器人: @yuyubabybot 个人频道 @yuyuoo9 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:27 UTC4 viewsread 15 November 2026
Photo

#阿拉山口 #个人兼职 #可上门 03年|身高170|胸围C ▪️身材火辣 温柔体贴 素质极佳 ▪️谈吐优雅 热情主动 甜美温柔 身体柔软解锁更多姿势💕 飞机: @cocoll3 双向机器人: @coco991bot 个人频道 @Cocoll6 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:27 UTC4 viewsread 15 November 2026
Photo

#阿图什 #个人兼职 #可上门 身高:168 体重:98斤 胸围:C 年龄:23 极品大秘,身材比例完美,腿长腰细屁股翘,胸型饱满圆润有手感,口技一流,服务好、好评多,上粉下嫩水多多,骚气放得开,热情似火。 飞机: @uulove1 双向机器人: @uuloveoobot 个人频道 @UUlove7 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

15 Nov 2026, 04:27 UTC3 viewsread 15 November 2026
Photo

#博乐 #个人兼职 #可上门 性格开朗 不催不事 身高169,体重92 02年,🐻C 只接素质课 🉑✈双️🉑🐍😘🉑第一人称🉑 🉑周边✌️ 飞机: @cocoll3 双向机器人: @coco991bot 个人频道 @Cocoll6 有教室 🉑外出 🉑包夜 面付 无需任何定金 诚信上课 . <👭同城老师信息公开群👉 @TXL48 >

14 Nov 2026, 18:08 UTC9 viewsread 14 November 2026
Photo

🏆美加墨世界杯🏆足球盛宴震撼来袭⚽️ 首存赠送100% 尊享VIP永久享受权益 超高返水1.2% 💎返水无上限无需流水、电子、真人0审核包出款 💎免实名、无需绑定手机号码 💎USDT存取款秒到账、大额无忧 🎰体育🎰真人🎰电子🎰棋牌🎰捕鱼 【 天天体育🌐官网 26299.xyz 】 🔰群主强烈推荐信誉大平台✅一起玩赚世界杯🔥

14 Nov 2026, 12:53 UTC34 views1 reactionsread 14 November 2026
Photo

#三明 #个人兼职 #已验证放心CJ 🍂第一次↓水♛短期兼职🍂 175cm 07年 🐻c 体重95 职业,学生北影兼职短期下海 ⭕️外好友纯兼職 🍂纯情学院风🍂 愛我不會後悔 留客神器,单单好评! ✅平台派单姑娘对接,没有中介✅ 💋788两个小时半~2000五个小时半💋 🐲服务:鸳鸯浴,舌吻,口活,360旋转吹,毒龙钻,69,胸推,臀推,亲咪咪,舔蛋蛋,丝袜高跟,情趣制服,观音坐莲,全套做爱,妹妹乖巧听话包你🈵意。 联系电报: @zmm1314 发不出消息联系: @xbbx329bot 后院频道:@zxz12371

👍1

14 Nov 2026, 12:53 UTC21 viewsread 14 November 2026
Photo

#石家庄 #个人兼职 #已验证放心CJ 清纯气质🌸理想女友✔️可盐可甜 可清纯 你的⭕️外女友 纯兼职 身高/167 • 𝐖𝐞𝐢𝐠𝐡𝐭体重/80 𝐁𝐮𝐬𝐭胸围/C 𝐀𝐠𝐞年龄/05年 全身无赘肉 S型身材 气质女友 暖心小女友 🍎配合各种姿势 🉑口🉑🐍 🉑69 🉑🛁 ✅平台派单姑娘对接,没有中介✅ 💋788两个小时半~2000五个小时半💋 🐲服务:鸳鸯浴,舌吻,口活,360旋转吹,毒龙钻,69,胸推,臀推,亲咪咪,舔蛋蛋,丝袜高跟,情趣制服,观音坐莲,全套做爱,妹妹乖巧听话包你🈵意。 联系电报: @zmm1314 发不出消息联系: @xbbx329bot 后院频道:@zxz12371

Showing the 12 most recent of 1,244 posts we hold for @xxp48. 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 recorded as deleted after publishing

We recorded 4 posts on @xxp48 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
8 August 2026
Most recent seen missing
3 September 2026
Median time before seen missing
9.0 hours
Seen missing in the last 30 days
0

Mentions

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

“同城附近人交友👩‍❤️‍👨” (@xxp48), 33,730 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/xxp48.

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.