hums pada out😔
Signed rest

Channel
@ortulukf
On this record: Topic · Previous handles · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Advertising · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
3subscribers
-1,496 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003304073428 |
|---|---|
| Type | Channel |
| Username | @ortulukf |
| Created | 1 January 2026 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 8 times, most recently 14 November 2026 |
| On Telegram | t.me/ortulukf |
Other / unclassifiable — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
@ortulukf was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @YourFuckerzOzil/160011 Aug 2026, 04:38 UTC | @ortulukf/13729 · this entry12 Aug 2026, 01:21 UTC | 1.00 | 21 hours |
| @YourFuckerzOzil/160911 Aug 2026, 09:34 UTC | @ortulukf/13728 · this entry12 Aug 2026, 01:15 UTC | 1.00 | 16 hours |
| @YourFuckerzOzil/161111 Aug 2026, 11:23 UTC | @ortulukf/15778 · this entry19 Aug 2026, 13:32 UTC | 1.00 | 8 days |
| @YourFuckerzOzil/161611 Aug 2026, 14:57 UTC | @ortulukf/13708 · this entry11 Aug 2026, 14:57 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @YourFuckerzOzil | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2 days | @YourFuckerzOzil (5–0) |
| @informasivirginia | 16 (8/8 hand-verifiable sample passed) | 1.00 | 2.3 hours | even |
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. 4 of the 4 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 372 comparable posts for this entry, running 18 July 2026 to 30 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @YourFuckerzOzil. 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 22:01 | 3 | +1 |
| 30 Aug 2026, 08:24 | 2 | -25,105 |
| 30 Aug 2026, 08:00 | 25,107 | no change |
| 30 Aug 2026, 07:45 | 25,107 | -371 |
| 29 Aug 2026, 07:28 | 25,478 | -18 |
| 28 Aug 2026, 08:28 | 25,496 | -17 |
| 27 Aug 2026, 07:28 | 25,513 | -11 |
| 26 Aug 2026, 09:33 | 25,524 | -9 |
| 25 Aug 2026, 06:12 | 25,533 | -1,322 |
| 24 Aug 2026, 07:18 | 26,855 | -2,887 |
| 22 Aug 2026, 13:36 | 29,742 | -833 |
| 21 Aug 2026, 02:26 | 30,575 | -74 |
| 19 Aug 2026, 23:33 | 30,649 | -264 |
| 18 Aug 2026, 20:26 | 30,913 | -785 |
| 17 Aug 2026, 19:07 | 31,698 | +1 |
| 16 Aug 2026, 17:46 | 31,697 | +131 |
| 15 Aug 2026, 06:17 | 31,566 | -86 |
| 13 Aug 2026, 23:27 | 31,652 | -12,082 |
| 12 Aug 2026, 14:54 | 43,734 | -1,664 |
| 11 Aug 2026, 15:43 | 45,398 | first reading |
754 posts held, back to 1 January 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 38 pages 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 754 posts for this entry, the most recent from 30 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 12 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 20260829101214141515010300166012095911837 | 1 | 29 August 2026 | 29 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 754 most recent posts we hold, published 1 January 2026 to 30 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
hums pada out😔
Signed rest
tawarin need 10
Signed rest
mem wajib on
Signed rest
need ch 1k mem gw take 25
Signed rest
p
Signed rest
NEED NOKTEL ID 1 DC 2 TAG SCAM + CH SCAM DANA 70😂
Signed rest
🗿🗿😭
Signed rest
@wheniyax ingpo tf la😅
Signed rest
inpo share nanti saya adminin );
Signed rest
🎉 GIVEAWAY #3772 🎁 Hadiah 1. saldo 1.000 — 1 winner ✅ Detail Giveaway Syarat Wajib Join: @pvcep, @asepoffc Participant: 14 Durasi: 2880 menit Berakhir: 01 Sep 2026 12:58 WIB ☎️ Claim Hadiah: @ibuIuwkwk
Signed GIVEAWAY
pilih
The shares total 114%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Signed rest
hms
Signed rest
Showing the 12 most recent of 754 posts we hold for @ortulukf. 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.
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
pilih
The shares total 114%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Habis Jumat 620p g.a apa??
The shares total 120%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 754 most recent posts we hold, published 1 January 2026 to 30 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 9 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.
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.
@ortulukf named 24 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
References a handle that is not a live channel — we have no record it ever was one.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“memek gede” (@ortulukf), 3 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/pvcep.
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.