Telegram RegisterThe public register of Telegram

Channel

.

@jdlskfog

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

2subscribers

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

Register entry

Telegram ID-1003034365243
TypeChannel
Username@jdlskfog
Created9 March 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live15 August 2026
Measurements held1
On Telegramt.me/jdlskfog

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 03:152first reading

Engagement

6 posts held, back to 9 March 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 9 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
17
Videos
1

Lifetime counters from Telegram’s own channel header, read 15 August 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
33s
Average length
33s

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.

Recent posts

9 Mar 2026, 12:57 UTC199 viewsread 15 August 2026

айди основы фрикетс : #ID7541428265 её новый юз : @friiketh

9 Mar 2026, 12:56 UTC186 viewsread 15 August 2026
Forwarded from @nyamcatNFTPhoto

моя лень меня спаслааа наху

9 Mar 2026, 12:56 UTC180 viewsread 15 August 2026
Forwarded from @L3n_NFTcfPhoto

Фрикетс наебала мою подругу на 4200 Айди скамера : @5591526713 не проводите щас сделки с фрикетс и тп, это пизда. налутали гифтов и игнорят 3+ людей уже 🌾 — @ShopNFT_Gift #скам | @NFTTGIFTbot

9 Mar 2026, 12:56 UTC183 viewsread 15 August 2026
Photo

@berlysip первые 7 нфт мои, гарантом была фрикетс @friketss. эти скрины единственная инфа. распространите, если хотите

9 Mar 2026, 12:56 UTC128 viewsread 15 August 2026
Forwarded from @NFTgifts_cfVideo

Бля тех у вопросы ну. У меня щас время уже 23:08.

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

Citation-graph rank — 576,853 of 1,480,688entries 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.

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 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.

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

“.” (@jdlskfog), 2 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/jdlskfog.

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.