Channel

Codigos DIÁRIOS 🦋

@diariamente

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

2,043subscribers

-266 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID	-1001112963994
Type	Channel
Username	@diariamente
Created	Between 1 February 2017 and 30 November 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	6 August 2026
Last confirmed live	4 October 2026
Measurements held	17
Confirmed unchanged	1 time, most recently 4 October 2026
On Telegram	t.me/diariamente

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. 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 first	Then	Overlap	Gap
@codigoskingslot/3703626 Aug 2026, 03:10 UTC	@diariamente/125222 · this entry6 Aug 2026, 03:10 UTC	1.00	under a minute
@codigoskingslot/3703636 Aug 2026, 03:10 UTC	@diariamente/125223 · this entry6 Aug 2026, 03:10 UTC	1.00	under a minute
@codigoskingslot/3703656 Aug 2026, 03:15 UTC	@diariamente/125225 · this entry6 Aug 2026, 03:15 UTC	1.00	under a minute
@codigoskingslot/3703676 Aug 2026, 03:15 UTC	@diariamente/125226 · this entry6 Aug 2026, 03:15 UTC	1.00	under a minute
@codigoskingslot/3703696 Aug 2026, 03:21 UTC	@diariamente/125229 · this entry6 Aug 2026, 03:22 UTC	1.00	under a minute
@codigoskingslot/3703756 Aug 2026, 04:03 UTC	@diariamente/125235 · this entry6 Aug 2026, 04:03 UTC	1.00	under a minute

Every channel this entry shares post bodies with
Channel	Matching posts	Text overlap	Typical gap	Published first
@codigoskingslot	21 (8/8 hand-verifiable sample passed)	1.00	under a minute	@codigoskingslot (19–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. 19 of the 19 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 39 comparable posts for this entry, running 6 August 2026 to 7 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).

Across the whole group of 2, the earliest publisher we hold is @codigoskingslot. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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.

KING CÓDIGOS Channel
@codigoskingslot · Channel3,116 subscribers

Growth

17 measurements spanning 60 days, net -266. 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 2,003–2,349 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
4 Oct 2026, 20:54	2,043	-40
25 Sept 2026, 07:39	2,083	-33
16 Sept 2026, 11:56	2,116	-17
12 Sept 2026, 11:56	2,133	-16
8 Sept 2026, 09:16	2,149	-20
3 Sept 2026, 10:56	2,169	-15
31 Aug 2026, 05:26	2,184	-11
28 Aug 2026, 03:27	2,195	-16
25 Aug 2026, 01:48	2,211	-17
21 Aug 2026, 19:05	2,228	-15
18 Aug 2026, 20:33	2,243	-12
15 Aug 2026, 19:53	2,255	-26
12 Aug 2026, 09:12	2,281	-17
9 Aug 2026, 01:21	2,298	-10
6 Aug 2026, 06:31	2,308	-1
6 Aug 2026, 05:51	2,309	no change
6 Aug 2026, 02:46	2,309	first reading

Engagement

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