Telegram RegisterThe public register of Telegram
Telegram profile photo for 奈奈生投稿社⛩️

Channel

奈奈生投稿社⛩️

@nanamitgs

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

120subscribers

+4 since we began measuring on 29 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002524997686
TypeChannel
Username@nanamitgs
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live15 November 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/nanamitgs

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 76% 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 7 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
@nanamitgs/220 · this entry21 Sept 2026, 12:07 UTC@uenoyamatgs/31621 Sept 2026, 12:08 UTC1.00under a minute
@nanamitgs/221 · this entry21 Sept 2026, 14:38 UTC@uenoyamatgs/32122 Sept 2026, 14:32 UTC1.0024 hours
@uenoyamatgs/31822 Sept 2026, 05:13 UTC@nanamitgs/223 · this entry22 Sept 2026, 05:13 UTC1.00under a minute
@uenoyamatgs/32223 Sept 2026, 04:52 UTC@nanamitgs/226 · this entry23 Sept 2026, 04:52 UTC1.00under a minute
@uenoyamatgs/32323 Sept 2026, 10:13 UTC@nanamitgs/227 · this entry23 Sept 2026, 10:13 UTC1.00under a minute
@uenoyamatgs/32524 Sept 2026, 05:28 UTC@nanamitgs/229 · this entry24 Sept 2026, 05:28 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
@uenoyamatgs8 (8/8 hand-verifiable sample passed)1.00under a minute@uenoyamatgs (6–2)
@mafuyutgs8 (8/8 hand-verifiable sample passed)1.00under a minute@mafuyutgs (5–3)
@jjzyxingqiutgs6 (6/6 hand-verifiable sample passed)1.00under a minuteeven
@argentitgs5 (5/5 hand-verifiable sample passed)1.00under a minute@argentitgs (3–2)
@huidiaorijitgs5 (5/5 hand-verifiable sample passed)1.00under a minute@huidiaorijitgs (3–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. 20 of the 20 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 14 comparable posts for this entry, running 21 September 2026 to 26 September 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 7 channels, the one whose matching posts we hold earliest is @jjzyxingqiutgs. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 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 7 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

116121118.529 September 2026 — 116 subscribers29 September 2026 — 116 subscribers14 October 2026 — 119 subscribers22 October 2026 — 121 subscribers29 October 2026 — 120 subscribers5 November 2026 — 119 subscribers15 November 2026 — 120 subscribers12029 September 202615 November 2026
7 measurements spanning 47 days, net +4. 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 115–122 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 07:57120+1
5 Nov 2026, 05:56119-1
29 Oct 2026, 08:00120-1
22 Oct 2026, 03:17121+2
14 Oct 2026, 01:18119+3
29 Sept 2026, 10:22116no change
29 Sept 2026, 09:47116first reading

Engagement

19 posts held, back to 21 September 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 19 posts for this entry, the most recent from 27 September 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

26 Sept 2026, 17:41 UTC2 viewsread 29 September 2026

彗星代投稿 出频道 𝐫𝐦𝟑/𝟏 人数𝟏𝟎𝟎 要的找 @hx1123

26 Sept 2026, 15:58 UTC3 viewsread 29 September 2026

彗星代投稿 📱✨ IP18系列 全新到货啦! 🎀 IP18|FULLSET 📦 全套齐全|现货可安排 🚚 西马邮寄 / 面交可询问 ☑ 下单前可确认颜色 & 容量 ☑ 安全包装发货 💰 最新价格 PM / 私聊询问 想要的宝子可以直接找我 🤍 先问不买也没关系~ 💭 下单 ┆ t.me/yasmine_071113 🎀 频道 ┆ t.me/yennnshoujipindao

26 Sept 2026, 15:36 UTC3 viewsread 29 September 2026
Photo

小冷代投稿 telegram @yyt_0913 WhatsApp 0182638166 ⋆接spay later 提现🥰 不够钱用?? 没事找我帮你解决问题🙋‍♀️ 全年无休🥰 Grab Later Boost Later RYT Later Atome 都有接🙋‍♀️❤️ spaylater提现一次抽25% grab 提现一次抽 35% 🙋‍♀️RM200起接✅ telegram私信下单 @yyt_0913 WhatsApp 0182638166

26 Sept 2026, 08:49 UTC2 viewsread 29 September 2026

彗星代投稿 出频道 𝐫𝐦𝟑/𝟏 人数𝟏𝟎𝟎 要的找 @hx1123

25 Sept 2026, 16:15 UTC2 viewsread 29 September 2026
Photo

小冷代投稿 telegram @yyt_0913 WhatsApp 0182638166 ⋆接spay later 提现🥰 不够钱用?? 没事找我帮你解决问题🙋‍♀️ 全年无休🥰 Grab Later Boost Later RYT Later Atome 都有接🙋‍♀️❤️ spaylater提现一次抽25% grab 提现一次抽 35% 🙋‍♀️RM200起接✅ telegram私信下单 @yyt_0913 WhatsApp 0182638166

25 Sept 2026, 09:05 UTC2 viewsread 29 September 2026
Photo

PLLI代投稿 ᅟ ˒ ⊹ 𝐏𝐞𝐚𝐜𝐡声播平台 🔍 大量缺主持陪陪! 无经验可教 对新手友好 ꒱ ▫️不限年龄 不限男女 ゠工资周结 ː 可马币&𝐳𝐟𝐛&台 不要害怕敢敢来𝐏𝐌我了解 ➰ 男孩女孩都不要害羞 ⦁ ֊ ⦁ 欢迎来看看呀 了解无需费用 没兴趣也没事❕ ✱ 一台手机 𝟎成本就能赚 ☑️ 不需露脸只需声音 - 𝐂𝐨𝐧𝐭𝐚𝐜𝐭 ⬞ @xhui5167 ✉️

25 Sept 2026, 05:01 UTC1 viewsread 29 September 2026

彗星代投稿 📱✨ IP18系列 全新到货啦! 🎀 IP18|FULLSET 📦 全套齐全|现货可安排 🚚 西马邮寄 / 面交可询问 ☑ 下单前可确认颜色 & 容量 ☑ 安全包装发货 💰 最新价格 PM / 私聊询问 想要的宝子可以直接找我 🤍 先问不买也没关系~ 💭 下单 ┆ t.me/yasmine_071113 🎀 频道 ┆ t.me/yennnshoujipindao

25 Sept 2026, 03:02 UTC3 viewsread 29 September 2026

彗星代投稿 ݂۫ 𝜗 最近在找投稿社嘛 𓈒۪۪۫  ❕快来看看这里𝐛𝐮𝐚⏖ ꒰꒰ 梦之所归投稿社 ۫ ۪𓈒ֵ  ིྀ 什么内容都可以投稿☑️ 𓏴 𝟏𝟖+ 𓏴 赌博 𓏴 投资 𓏴 🍥⋮ 接稿管理在𝗣𝗶𝗻 ᵔ ˲ ̫ ˱ ᵔ ɴᴇᴇᴅ跟格式投稿! ♯ @mzsgtgs 〉

24 Sept 2026, 05:28 UTC5 viewsread 29 September 2026

彗星代投稿 📢 𝐅𝐁 发帖 & 评论员|学生兼职 有 𝐅𝐁 账号,平时又不知道可以拿来做什么? 想利用空闲时间赚一点奶茶钱、零花钱?🧋💰 💼 工作内容很简单: 👇🏻 📌 𝐅𝐁 发帖 按照指定要求,在相关 FB 小组发布指定内容。 💬 𝐅𝐁 评论 按照要求,在符合条件的帖子下面进行简单回复。 💰 计件计算,多做多得 🔥 发帖:𝟎.𝟎𝟔 / 𝟏 个 🔥 评论:𝟎.𝟎𝟔 ~ 𝟎.𝟎𝟖 / 𝟏 个 不是固定月薪,属于按完成数量计算。 有时间就多做一点,没时间就少做一点,比较适合学生利用课余时间慢慢做。 🎓 特别适合学生: ✅ 放学后有空可以做 ✅ 周末有时间可以做 ✅ 不需要每天固定上班 ✅ 有 FB 账号即可了解工作 ✅ 有经验可以长期合作 ✅ 没有经验也可以来,我会教基本操作 不会做不用担心,前期会说明工作要求和操作方式,熟悉之后再自己慢慢做。 ⚠️ 结账方面提前说明 有时候工作量比较多,结账可能会有所延迟,不是…

23 Sept 2026, 13:03 UTC2 viewsread 29 September 2026

PLLI代投稿 📮 有业务,就来投稿! 不管你是老板、代理、卖家还是个人创业者 都可以来这里分享你的业务 ✨ 🛍️ 产品|服务|店铺|优惠|业务介绍 📢 让更多人看见你的业务! 🔗 @postyourbiz

23 Sept 2026, 10:13 UTC5 viewsread 29 September 2026

彗星代投稿 ˖ 𓍢ִ 不想再 𝟏 个 𝟏 个自己找 ֪ ׅ ֹ ₊˚ 投稿社链接了𝐦𝐚𝐚«❔ 얼른 보세요 𓈒ׁ 彗星 𓏼 준비했어요 ݁˖ @argentitgs <𝟑 ⟳ @chuuyatgs ” :: @uenoyamatgs ୨୧ ⊹ @mafuyutgs * ‎𐙚 @nanamitgs ‧˚ ⓘ 𝗡𝗼 ‘ 𝟣𝟪+ ; 赌博 ; 投资 ; 烟 * 投稿 𝐟𝐢𝐧𝐝 @hx1123 %

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

Mentions

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

“奈奈生投稿社⛩️” (@nanamitgs), 120 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/nanamitgs.

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.