Telegram RegisterThe public register of Telegram
Telegram profile photo for 南部資訊

Channel

南部資訊

@jkfa269

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

15subscribers

+2 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003929146380
TypeChannel
Username@jkfa269
CreatedBetween 1 April 2026 and 15 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live19 November 2026
Measurements held6
Confirmed unchanged6 times, most recently 19 November 2026
On Telegramt.me/jkfa269

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 77% 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 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@jkfa269/917 · this entry15 Jul 2026, 05:48 UTC@fba267/164415 Jul 2026, 06:54 UTC1.0065 minutes
@jkfa269/921 · this entry16 Jul 2026, 05:35 UTC@fba267/166516 Jul 2026, 06:17 UTC1.0042 minutes
@jkfa269/923 · this entry16 Jul 2026, 05:35 UTC@fba267/166216 Jul 2026, 06:17 UTC1.0041 minutes
@jkfa269/926 · this entry16 Jul 2026, 05:36 UTC@fba267/166016 Jul 2026, 06:16 UTC1.0040 minutes
@jkfa269/928 · this entry16 Jul 2026, 05:36 UTC@fba267/165516 Jul 2026, 06:16 UTC1.0040 minutes
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
@fba2675 (5/5 hand-verifiable sample passed)1.0041 minutesthis entry (5–0)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 15 July 2026 to 2 August 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 @jkfa269 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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 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

1315148 August 2026 — 13 subscribers12 August 2026 — 13 subscribers30 August 2026 — 14 subscribers17 September 2026 — 15 subscribers1 October 2026 — 14 subscribers12 October 2026 — 15 subscribers8 August 202612 October 2026
6 measurements spanning 64 days, net +2. 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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 05:2015+1
1 Oct 2026, 15:5514-1
17 Sept 2026, 01:3915+1
30 Aug 2026, 16:2714+1
12 Aug 2026, 04:0113no change
8 Aug 2026, 20:3213first reading

Engagement

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

Recent posts

2 Aug 2026, 18:53 UTC3 viewsread 12 August 2026
Forwarded from @mt16990Photo

#高雄新人 點心 160cmC奶19歲 #前幾天剛面試的 小小只蠻可愛的 身材瘦瘦的 聲音也很好聽 就那種溫柔 貼心 甜美的乖乖女哦 #床上需要多多開發 嘻嘻 🌈Line:mt160 🌈Gleezy:mt160 🌈Telegram:@mt1689 營業時間: 13:00~4:00 📌商城下次Gleezy選妃交流群組:https://c.gleezy.top/4nuZaI0L 🍀北部專區:@mt1678 🍀中部專區:@mt03344 🍀南部專區:@mt16890 🍀新竹專區:@mt1650 🍀學生妹18~22歲:@mt16990 🍀大奶巨乳熟女:@mt16789 🍀人妻熟女專區:@mt5271 #台灣外送茶 #台灣出差找小姐 #高檔茶 #學生妹試車 #旅館一夜情 #口碑茶 #無套內射 #巨乳

2 Aug 2026, 18:52 UTC4 viewsread 12 August 2026
Forwarded from @mt1630Photo

林品茹164 46kg D奶 23歲 淫蕩慾女 欲求不滿 喜挑戰極限 氣質外貿 修長的美腿 口交技術棒 超會挑逗 🌈Line:mt160/bk638 🌈Gleezy:mt160 🌈Telegram:@mt1689 營業時間: 13:00~4:00 📌商城下次Gleezy選妃交流群組:https://c.gleezy.top/4nuZaI0L 🍀北部專區:@mt1678 🍀中部專區:@mt03344 🍀南部專區:@mt16890 🍀新竹專區:@mt1650 🍀學生妹18~22歲:@mt16990 🍀大奶巨乳熟女:@mt16789 🍀人妻熟女專區:@mt5271 #台灣外送茶 #台灣出差找小姐 #高檔茶 #學生妹試車 #旅館一夜情 #口碑茶 #無套內射 #巨乳

2 Aug 2026, 18:52 UTC3 viewsread 12 August 2026
Forwarded from @mt1630Photo

#新妹下海 #孕婦 喜歡快來搶頭香 #無毛孕婦 鮑魚乾淨性慾強孕期比較特殊 老公又長期出差在外每天都寂寞難耐忍不住想打砲的心 奈奈165 D 47kg 27歲 🌈Line:mt160/bk638 🌈Gleezy:mt160 🌈Telegram:@mt1689 營業時間: 13:00~4:00 📌商城下次Gleezy選妃交流群組:https://c.gleezy.top/4nuZaI0L 🍀北部專區:@mt1678 🍀中部專區:@mt03344 🍀南部專區:@mt16890 🍀新竹專區:@mt1650 🍀學生妹18~22歲:@mt16990 🍀大奶巨乳熟女:@mt16789 🍀人妻熟女專區:@mt5271 #台灣外送茶 #台灣出差找小姐 #高檔茶 #學生妹試車 #旅館一夜情 #口碑茶 #無套內射 #巨乳

16 Jul 2026, 05:36 UTC21 viewsread 12 August 2026
Photo

白楚楚 170公分 大C罩杯 48kg 25歲 身材比例極好、腿長腰細、曲線明顯 適合:腿控|高挑控|氣場系戀愛感 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy:jkf0077 💗Line:rely168 💗私密蜜蜜TG:@jkf0077 🍀北部喝茶班表:@jkfa288 🍀中部喝茶班表: @jkfa147 🍀南部喝茶班表: @jkfa269 🍀學生妹18~22歲:@jkf247 🍀熟女人妻大奶區:@jkfa366 🍀特別重口味專區:@jkfq963

16 Jul 2026, 05:36 UTC19 viewsread 12 August 2026
Photo

今日長腿上線 💕 名字:漫天 💕 身材:168.47.C.25歲 氣質 身材好 皮膚粉嫩粉嫩der 鮑魚緊實多汁 身體敏感稍微挑逗挑逗就濕濕了喔 服務很好 態度好喔 可變裝 不趕時間~ 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy:jkf0077 💗Line:rely168 💗私密蜜蜜TG:@jkf0077 🍀北部喝茶班表:@jkfa288 🍀中部喝茶班表: @jkfa147 🍀南部喝茶班表: @jkfa269 🍀學生妹18~22歲:@jkf247 🍀熟女人妻大奶區:@jkfa366 🍀特別重口味專區:@jkfq963

16 Jul 2026, 05:35 UTC13 viewsread 12 August 2026
Photo

安琪 165cm 50kg Ecup 25歲 腰細、肩線美、腿長又緊實,身材完美 女上位狠又穩,力量感很強,你完全只需要躺著受 口活夠深、夠準、夠刺激 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy:jkf0077 💗Line:rely168 💗私密蜜蜜TG:@jkf0077 🍀北部喝茶班表:@jkfa288 🍀中部喝茶班表: @jkfa147 🍀南部喝茶班表: @jkfa269 🍀學生妹18~22歲:@jkf247 🍀熟女人妻大奶區:@jkfa366 🍀特別重口味專區:@jkfq963

16 Jul 2026, 05:35 UTC9 viewsread 12 August 2026
Photo

思詩 165cm 49kg D奶 26歲 第一眼是斯文OL,但只要進房間立刻變【小騷貨模式】 奶泡強、喇舌黏、叫聲不刻意,是濕、是色、是真刺激 最會邊騎邊看你眼睛那種,男生完全招架不住 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy:jkf0077 💗Line:rely168 💗私密蜜蜜TG:@jkf0077 🍀北部喝茶班表:@jkfa288 🍀中部喝茶班表: @jkfa147 🍀南部喝茶班表: @jkfa269 🍀學生妹18~22歲:@jkf247 🍀熟女人妻大奶區:@jkfa366 🍀特別重口味專區:@jkfq963

15 Jul 2026, 05:48 UTC10 viewsread 12 August 2026
Photo

念柔 170cm-46kg-D奶-21歲 OMG!麻豆兼職絶美大長腿美少女 膚白到發光像白雪公主 顔值高到犯規 腿長又直又細 身材比例完美 外表清純漂亮 整體又高挑又仙 超級吸睛 熱綫⤵️⤵️⤵️⤵️⤵️ 💗Gleezy:jkf0077 💗Line:rely168 💗私密蜜蜜TG:@jkf0077 🍀北部喝茶班表:@jkfa288 🍀中部喝茶班表: @jkfa147 🍀南部喝茶班表: @jkfa269 🍀學生妹18~22歲:@jkf247 🍀熟女人妻大奶區:@jkfa366 🍀特別重口味專區:@jkfq963

Showing the 8 most recent of 8 posts we hold for @jkfa269. 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.

Forward network

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

“南部資訊” (@jkfa269), 15 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/jkfa269.

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.