Telegram RegisterThe public register of Telegram
Telegram profile photo for 光之国の故事

Channel

光之国の故事

@GZGDGS666

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

69,646subscribers

+27,161 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-1002253386095
TypeChannel
Username@GZGDGS666
Description本人:@dyna888888 光之国群聊:https://t.me/GZGchat666 光之国福利频道:https://t.me/GZGFULI1 导航/榜单频道:https://t.me/GZGPilot
CreatedBetween 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/GZGDGS666

Topic

Adult — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@GZGDGS666/1343 · this entry3 Aug 2026, 05:15 UTC@onehundredtravel/16567 Aug 2026, 03:44 UTC1.004 days
@onehundredtravel/170314 Aug 2026, 04:03 UTC@GZGDGS666/1366 · this entry14 Aug 2026, 04:04 UTC1.0072 seconds
@onehundredtravel/16352 Aug 2026, 09:47 UTC@GZGDGS666/1378 · this entry20 Aug 2026, 08:34 UTC1.0018 days
@GZGDGS666/1397 · this entry26 Aug 2026, 23:29 UTC@onehundredtravel/175426 Aug 2026, 23:29 UTC1.00under a minute
@GZGDGS666/1402 · this entry1 Sept 2026, 08:53 UTC@onehundredtravel/17892 Sept 2026, 07:22 UTC1.0022 hours
@GZGDGS666/1343 · this entry3 Aug 2026, 05:15 UTC@MmFulidafangsong/20610 Aug 2026, 01:31 UTC1.007 days
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
@onehundredtravel9 (8/8 hand-verifiable sample passed)1.0022 hours@onehundredtravel (5–4)
@MmFulidafangsong6 (6/6 hand-verifiable sample passed)1.006 daysthis entry (4–2)

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. 6 of the 6 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 111 comparable posts for this entry, running 30 July 2026 to 12 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 2 channels, the one whose matching posts we hold earliest is @GZGDGS666 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 13 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 2 registered channels linked by matching posts. 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

42,48569,64656,065.57 August 202611 November 2026
63 measurements spanning 96 days, net +27,161. 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 38,411–73,720 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
11 Nov 2026, 22:2069,646+416
9 Nov 2026, 21:5869,230+465
8 Nov 2026, 10:4968,765+289
7 Nov 2026, 07:5168,476+211
6 Nov 2026, 05:3668,265+195
5 Nov 2026, 06:2168,070+199
4 Nov 2026, 08:3067,871+196
3 Nov 2026, 08:1967,675+74
2 Nov 2026, 08:4967,601-4
1 Nov 2026, 05:5167,605+210
31 Oct 2026, 07:0867,395+192
30 Oct 2026, 06:2867,203+869
29 Oct 2026, 03:1066,334+420
28 Oct 2026, 04:0765,914+448
27 Oct 2026, 02:5765,466+316
26 Oct 2026, 03:4765,150+316
25 Oct 2026, 04:2764,834+265
24 Oct 2026, 05:2564,569-14
23 Oct 2026, 02:1064,583+413
21 Oct 2026, 22:3164,170first reading

Engagement

150 posts held, back to 30 July 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 211 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
27.4%
avg views ÷ 69,646 subscribers
Avg views / post
19,100
45 posts measured
Reaction rate
0.392%
reactions ÷ views · ER floor
Posts in window
45
of 150 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 12 November 2026
Posts held150 (30 July 2026 – 12 November 2026)
Views total858,300
Reactions total3,362
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 22:50 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
155
Videos
38
Links
162

Lifetime counters from Telegram’s own channel header, read 13 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
6m 12s
Average length
12s

Measured directly from 32 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

8,971 reactions across 146 posts, in 14 distinct kinds. The most used accounts for 93.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤8,38593.5%
👍3964.41%
💩760.847%
🔥360.401%
👎280.312%
👏150.167%
🥰80.089%
💯60.067%
🤡60.067%
🥴50.056%
🤯40.045%
😱30.033%
😁20.022%
🤔10.011%

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 148 of the 150 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 8,971 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 150 most recent posts we hold, published 30 July 2026 to 12 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: 15 of 45 posts held from the last 30 days (33.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).

12 Nov 2026, 15:20 UTC≈7,500 views183 reactionsread 13 November 2026
Photo

#成都 #嫩妹 #蛇精 #精品 【怪獣の名】安诺 【奧特の名】#无流 【怪獣の牌】@annuoya 【怪獣の價】800/P(报告减一) 【怪の硬件】青春靓丽嫩妹一枚,十八九岁左右,人照相似度高,接近九分像,真人五官秀气,很符合我审美,问了下竟然是江南妹妹,怪说不得有股子温婉的气质,完全不土不精神,穿着个吊带,看起来又清纯又魅惑,皮肤偏白,正面肤质好,背后略有痘印,进门见到人,还没脱衣服鸡儿就开始起立了,颜值完全是我的菜。身高165不到,比较显高挑,腿又长又细,比筷子腿略多一份肉感,把玩起来让人爱不释手,b+的胸盈盈一握,乳头颜色偏淡,胸很软但是不塌,形状好看,最要命的是腰臀比也非常优越(详见视频),简直是想跳过鸳鸯浴环节直接把她就地正法。 【怪の軟件】陪洗仔细,刚下海的妹妹服务不多,就是嫩妹三件套,舌吻过程中会主动叫我配合伸舌头,让我用她喜欢的方式接吻,很少见这么落落大方的妹妹,口技普通,但眼神带电,口的…

❤182🔥1

11 Nov 2026, 07:56 UTC≈10,300 views29 reactionsread 13 November 2026
Photo

#成都 #嫩妹 #小蛇 #良品 【怪獣の名】#思思 【奧特の名】#无流 【怪獣の牌】@Ssisi09 【怪獣の價】600/P 【怪の硬件】人照相似度8.5分,参考性比较高,萝莉风格的长相和妆容,不算通常意义的好看,不过个人觉得还过得去。 身材不胖不瘦,骨架小,胸大概是b,水滴型,手感好,屁股有肉比较翘,后入观感佳,背部皮肤痘痘和痘印都有一些,有点影响整体美观,但还算能接受。ps:牙不太好,应该是被磕到过。 bb方面:户型小蝴蝶,阴唇饱满,颜色比较粉嫩。 【怪の軟件】三件套(没有口爆),口技高超,很会刺激敏感点。差点给我口出来了。 昆感方面:紧度中上,湿度中上,后入包裹感更明显,昆感很好,今天日了十分钟就交货了。 【玉玉の足】36码埃及脚,指节分明,形状好看,没做美甲,基本无死皮,背部有一定青筋,但也够得着玉足基准线看。 【奧特总结】人照相似度不错的小矮矮萝莉妹子,具体看个人审美,口技特别好,喜欢照片的…

❤29

10 Nov 2026, 08:28 UTC≈12,400 views112 reactionsread 13 November 2026
Photo

#成都 #嫩妹 #小蛇 #精品 【怪獣の名】#小鱼儿 【奧特の名】#戴拿 【怪獣の牌】@doux91 【怪獣の價】700/P 【怪の硬件】人照相似度8.5-9的样子,小狗眼很可爱~身材163/85左右,肤色偏白,皮肤除了有新干燥之外状态尚可。 罩杯对A奶嘴浅色;腰部无赘肉;屁股蝴蝶臀肉感不错;腿有点像酒杯腿非常不错! 户型方面:人工白虎馒头比,不过有些毛桩长出来了,后续赚到钱了会去激光脱毛的。 【怪の軟件】确实是第一次下水的妹妹,态度很不错,非常谦虚的学习,老司机真可以去好好调教了。 服务方面:不是很熟练,但真是特别听话,说啥都配合。口得不算久,但口技还算合格无齿感,小蛇也算比较配合吧。 昆感方面:紧度适中、温度适中、湿度上佳、反馈感中上!这妹妹反馈很真实,想叫又不敢叫的样子,时不时轻哼一声“好爽”肏到后面还有很多白浆~ 【玉玉の足】36码足,足底很嫩,但玉足没怎么保养,还差一点到食品级。 【奧特总结…

❤108👍2🤡2

10 Nov 2026, 04:39 UTC≈11,500 views5 reactionsread 13 November 2026
Forwarded from @cdloveclubPhoto

✨双11重磅回馈,双店同庆福利炸场✨ 💥2000元月卡,共5次到店体验*(双店通用) ⚠️本次套餐限购30张,先抢先得! 📢温馨提示:本卡和年卡储蓄会员换卷用户,不能与本卡同时使用,有限期30天(过期作废),一人限购一张(仅到店) 限时福利,手慢无,欢迎预约 截止至11.11号晚23.59停止办理 联系客服:啵啵

❤5

9 Nov 2026, 15:03 UTC≈12,900 views5 reactionsread 13 November 2026

苏洛老号炸了,下面是新号 ⬇️⬇️⬇️ @suluofuhuo

❤5

8 Nov 2026, 03:52 UTC≈17,800 views165 reactionsread 13 November 2026
Video

#成都 #嫩御 #蟒蛇 #极品 【怪獣の名】#念一 【奧特の名】#小土豆 【怪獣の牌】@nianyiya 【怪獣の價】800/P 【怪の硬件】身高165,体重90斤,19岁,颜值我能给到9.5分(但这是个人评分),甜御风少女~ 但念一随时都在笑,就很融化心,小虎牙笑起来真好看,嘟嘟嘴是真乖,刚满18岁の周迅既视感! 屁股肉嘟嘟,富有弹性,身材很好,腰细屁股翘,B胸掌中宝,一手捏住,皮肤嫩,丝滑触感,正常肤色,一线天,阴部周围居然有粉嫩红晕一圈。 【怪の軟件】态度情绪价值极高,甚有女友感,特别懂男人,进门放下书包,就大大的拥抱亲亲,坐在床边就跳你腿上坐着抱抱亲亲,主动帮脱、放、陪浴、擦身体,一直找话题,i人福音! 三件套加舔胸,口技甚好,咵咵水声,不是只攻击头部,而是沉浸式环绕包裹,深喉有抵住挤压感,且口水流向改变,感受明显,让人倒吸一口凉气。 昆感方面:紧度上佳、温度中上、湿度上佳、反馈感上佳!不能回想,…

❤155👍10

6 Nov 2026, 13:23 UTC≈20,700 views189 reactionsread 13 November 2026
Photo

#成都 #大胸 #蟒蛇 #精品 【怪獣の名】#笨笨 【奧特の名】#戴拿 【怪獣の牌】@benben20003 【怪獣の價】600/P 【怪の硬件】人照相似度9层左右,颜值普通水平。身材160/110左右,皮肤状态很好,肤色冷白皮。 罩杯对D纤体乳;小肚子比较明显;屁股属于大肉臀;腿也是小肉腿。 户型方面:人工白虎馒头比,好看的不得了。 【怪の軟件】态度很不错,课室环境也干净,挺会调琴的,本来疲惫的小戴拿都立马起立了。但是没有陪洗的。 服务方面:口技很不错,能口很久,会挑逗敏感点。舌吻也很主动,还会主动搂着脖子蛇,蛇管够。 昆感方面:紧度中上、温度中上、湿度中上、反馈感上佳。各种姿势都会,会主动抱着你,确实让人很投入。 【玉玉の足】36码小肉足,足底很红润,美甲也很好看,也达到食用级别。 【奧特总结】冷白皮bbw,身材不错,但脸很普通。胸控可以闭眼冲~ 点赞100发布福利视频! 光之國の故事 htt…

❤184🔥4👎1

5 Nov 2026, 14:46 UTC≈18,700 views14 reactionsread 13 November 2026

皎皎福利视频已发送! ⬇️⬇️⬇️ https://t.me/GZGFULI1/301

❤14

5 Nov 2026, 10:54 UTC≈19,000 views145 reactionsread 13 November 2026
Photo

#成都 #嫩妹 #蟒蛇 #精品 【怪獣の名】#可星 【奧特の名】#56 【怪獣の牌】@kxx5201 【怪獣の價】700/P 【怪の硬件】人照相似度一般,但真人颜值还可以,可爱型嫩妹,有点土气,比较青涩。 身材偏瘦但不是排骨精,胸大概为b,小但是算挺拔,乳头略大很饱满,腿和屁股有点肉,手感很好,另外基本没啥小肚子。 bb方面:小蝴蝶,水多,比较嫩。 【怪の軟件】三件套,刚开始话不多,舌吻比较被动但是很配合,态度很好,打开话匣子后还是能感觉是个很可爱的妹妹。 昆感方面:紧度较紧,湿度中上,做爱比较被动,反应一般,插的深的话才会有明显回馈,有点痛苦面具但是做了三十分钟也没有催的意思,妹子会夹,切换到后入给我勒的青痛,总体做爱体验尚可 【玉玉の足】36码,足型不错,日常打理养护一般,也没有做美甲,算是普通玉足。 【奧特总结】颜值可爱的青涩嫩妹,气质有点土,软件偏被动,除了化妆技术有点一般,要抽烟之外没啥缺点…

❤145

5 Nov 2026, 04:57 UTC≈17,400 views11 reactionsread 13 November 2026
Video

兄弟们,给大家推荐一家: 成都商K · 情趣换装 ·🥰 真空裸嗨 · 大游戏互动场🥰 🥰 热门玩法节选:高山流水|冰火两重天|鸳鸯戏水|七星瓢虫|汉堡包… 等等几十种福利荤游戏🥰 玩法不止有趣,更是贴身挑逗❗️ 让人欲罢不能❗️流连忘返❗️ 🥰 中场黑灯环节 全程高能释放❗️ 📱沉浸式暗场互动,黑灯劲舞开场,弯腰、翻身、对坐、贴靠——性感身段近在咫尺 每一步走位都在勾引神经,每一处接触都引爆荷尔蒙❗️ 🥰 每日佳丽出勤打底150+ 🚫📛📛📛🅱️✴️🅰️🆚🚫🆑 形象佳、配合度高,现场海选 先选人后消费❗️📱📱📱📱 🔗成都预定 🔗玩法介绍 🔗全国预定 🔗店铺直达 🔗组队群聊 🔗组队规则 📞👍 19382386106 #成都商K #真空战袍游戏场

❤11

4 Nov 2026, 12:55 UTC≈18,900 views133 reactionsread 13 November 2026
Photo

#成都 #嫩御 #小蛇 #精品 【怪獣の名】#皎皎 【奧特の名】#戴拿 【怪獣の牌】@JJ2006ab 【怪獣の價】700/P 【怪の硬件】人照相似度8.5左右,有点嫌弃脸的意思了。身材170/90左右,高挑纤细。肤色正常偏黄,皮肤状态一般。 罩杯对C浅褐色奶嘴;腰身纤细无赘肉;屁股蝴蝶臀有肉感;大长腿笔直线条很好。 户型方面:一线天和蝴蝶的结合,毛量较少。 【怪の軟件】课室环境不错,妹妹才长休回来,状态很好,态度也比之前热情不少。 服务方面:口技过关,能口很久,蛇也比较配合。 昆感方面:紧度中上、温度适中、湿度中上、反馈感中上。妹妹身材是真的好啊,视觉效果是真不错,听着轻轻的呻吟确实是干劲十足。 【玉玉の足】37码细长型,美甲好看,足弓也好看,食用级别! 【奧特总结】身材特别好的妹妹,之前状态不稳定,但是这次回来状态很不错,吃这一口的兄弟可以冲! 点赞100发福利视频! 🔣🔣点击评论区查看实拍🔣…

❤133

3 Nov 2026, 12:57 UTC≈16,300 views181 reactionsread 13 November 2026
Photo

#成都 #嫩妹 #蛇精 #精品 【怪獣の名】#十月 【奧特の名】#戴拿 【怪獣の牌】@CDthwa 【怪獣の價】500/P 【怪の硬件】颜值和照片8.5层现实度,身材162/105左右微胖。正常肤色,全身符文爽爆了!皮肤状态一般。 罩杯对C+奶嘴浅褐色;有一点点小肚子不影响的程度;大肉臀弹性十足腰臀比也不错;腿就正常有点肉感的腿。 户型方面:人工白虎馒头比,但长了一点毛茬。 【怪の軟件】话不多,但服务态度比较积极,会主动提出来陪洗,洗的也蛮仔细的。也能简单聊天对于嫩妹来说算不错了。 服务方面:口技不错,无齿感且口的时间很久,口一下还会专攻一下码眼~蛇纹也很配合,能蛇抱。 昆感方面:紧度中上、温度中上、湿度适中、反馈感中上。非常的配合每一个姿势,而且全身符文带给我的视觉效果是无法比拟的,很刺激! 【玉玉の足】36码足,足型不错,足底也红润,但不太注重保养,差一点到食用级。 【奧特总结】500吃一个嫩妹符…

❤171👍10

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

@GZGDGS666 edited 9 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
11 August 2026
Most recent edit
17 October 2026

Posts recorded as deleted after publishing

We recorded 15 posts on @GZGDGS666 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
11 November 2026
Median time before seen missing
7 days
Seen missing in the last 30 days
7

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“光之国の故事” (@GZGDGS666), 69,646 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/GZGDGS666.

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.