Channel
@ExpertodeTelegram
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
9subscribers
+0 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001906650796 |
|---|---|
| Type | Channel |
| Username | @ExpertodeTelegram |
| Description | Un proyecto de @LatinTelegramFreaks @CountriesFreaks @GenRevolutionOfficial @AppleStyleOfficial Necesitas más ayuda? @UsarTelegramEspanol @BuscarCanalesTelegram @LensTelegram @ContactarTelegram @denunciardelitotelegram @NoticiasTelegramEspanol |
| Created | 28 May 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ExpertodeTelegram |
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 11 November 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
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 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @ExpertodeTelegram/6 · this entry28 May 2023, 23:39 UTC | @IntroduccionTelegram/628 May 2023, 23:40 UTC | 1.00 | under a minute |
| @IntroduccionTelegram/728 May 2023, 23:40 UTC | @ExpertodeTelegram/7 · this entry28 May 2023, 23:41 UTC | 1.00 | under a minute |
| @ExpertodeTelegram/8 · this entry28 May 2023, 23:41 UTC | @IntroduccionTelegram/828 May 2023, 23:42 UTC | 1.00 | under a minute |
| @ExpertodeTelegram/9 · this entry30 May 2023, 16:11 UTC | @IntroduccionTelegram/1630 May 2023, 16:11 UTC | 1.00 | under a minute |
| @ExpertodeTelegram/12 · this entry25 Feb 2024, 08:25 UTC | @IntroduccionTelegram/1925 Feb 2024, 08:27 UTC | 1.00 | 2 minutes |
| @IntroduccionTelegram/2229 Feb 2024, 10:42 UTC | @ExpertodeTelegram/15 · this entry29 Feb 2024, 10:55 UTC | 1.00 | 14 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @IntroduccionTelegram | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (4–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. None of the 2 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 28 May 2023 to 15 March 2025. 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 @ExpertodeTelegram — 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.
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 |
|---|---|---|
| 12 Aug 2026, 11:48 | 9 | no change |
| 12 Aug 2026, 02:49 | 9 | first reading |
12 posts held, back to 28 May 2023 — 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 12 posts for this entry, the most recent from 15 March 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
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.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 17 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 29 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
6 minutos que cambiarán tu vida en Telegram PARA SIEMPRE! Estamos mostrando SÓLO ALGUNOS!!! de las funciones disponibles, que hacen de TELEGRAM EL MEJOR SOCIAL DEL MUNDO! (incluso si la gente todavía no entiende eso 🤦♂️...) https://t.me/NoComparisonTelegram SÍ, TELEGRAM TAMBIÉN ES EL MEJOR SOCIAL PARA LA CIENCIA! https://t.me/GenRevolutionOfficial/212 Más información https://t.me/JoinShareableChatFolders/16 Music…
Telegram @JoinShareableChatFolders para tontos: a) ahora nos hemos dado cuenta de que ningún usuario premium no puede ver más de 100 canales ... en este caso puede utilizar, por ejemplo, nuestra lista máxima de 100 canales https://t.me/addlist/eaqHVCVl4lZlYTIx https://t.me/addlist/q0dAcDb0RSc5NmQx hasta que Telegram solucione ese problema de alguna manera... b) NO NECESITA unirse a todos los canales si no está inte…
Sticker, posted without a caption
Una de las peores cosas que puede hacer un Telegram Freaks es pensar "No necesito dos aplicaciones de Mac!". Nunca y de nuevo NUNCA! use solo una aplicación de Mac, excepto si quiere ser como los usuarios promedio que pierden el 50% de las funciones sin siquiera poder encontrar los canales de Telegram correctamente. Ambas aplicaciones son totalmente diferentes y no pueden considerarse alternativas.
Si está utilizando aplicaciones Mac basadas en Telegram Desktop (Bettergram, Desktop, Kotatogram, iMe, Telegreat, Telegram Lite, Desktop Beta), entonces necesita cambiar al menos una opción: 1: Configuración/Avanzado/Administrar almacenamiento local —> mínimo 2: Configuración / Avanzado / Descarga automática de medios / En chats privados / grupos / canales -> opcionalmente puede desactivarlo
Bien, y ahora? Cómo puedo hacer eso? La respuesta es bastante simple. Depende de qué aplicación MacOS estés usando. Si está utilizando Telegram para MacOS (estable o Beta Apple CPU compatible o no), debe cambiar la siguiente opción: Configuración/Datos y almacenamiento/Uso de almacenamiento -> Tamaño máximo de caché al mínimo y eliminación automática después de 1 día para las tres opciones.
Sí, sabemos que quieres saber qué es lo más importante que deben hacer los Telegram Freaks, pero lo siento, debes esperar. Veamos cuál es la segunda cosa más importante que puede hacer en Telegram: seguro que podrá administrar el almacenamiento de manera adecuada!
Channel photo updated
Channel photo removed
Channel created
Showing the 12 most recent of 12 posts we hold for @ExpertodeTelegram. 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.
Named by 2 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Las cosas más importantes que deben hacer los Telegram Freaks” (@ExpertodeTelegram), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ExpertodeTelegram.
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.