Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇲🇽 USA Visa TN Appointments | 🇲🇽 Visado TN Citas Estados Unidos

Channel

🇲🇽 USA Visa TN Appointments | 🇲🇽 Visado TN Citas Estados Unidos

@usa_visa_tn_mexico

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

544subscribers

-6 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-1002474692075
TypeChannel
Username@usa_visa_tn_mexico
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/usa_visa_tn_mexico

Topic

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 73% 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.

Growth

544553548.58 August 2026 — 550 subscribers8 August 2026 — 550 subscribers15 August 2026 — 553 subscribers23 August 2026 — 550 subscribers30 August 2026 — 546 subscribers9 September 2026 — 545 subscribers18 September 2026 — 544 subscribers8 August 202618 September 2026
7 measurements spanning 42 days, net -6. 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 543–554 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:18544-1
9 Sept 2026, 08:18545-1
30 Aug 2026, 02:13546-4
23 Aug 2026, 01:28550-3
15 Aug 2026, 16:54553+3
8 Aug 2026, 03:45550no change
8 Aug 2026, 00:21550first reading

Engagement

20 posts held, back to 14 May 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 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 20 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 14 May 2026 to 4 June 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Jun 2026, 02:18 UTC352 views1 reactionsread 8 August 2026
Forwarded from @usa_visas_mx

❗️ Próxima subida del precio de la suscripción. Dado que estamos recibiendo demasiadas solicitudes de suscripción, a partir del sábado 6 de junio, el precio de la suscripción a los canales de notificaciones privadas aumentará en un 50 %. El precio de la suscripción no variará para quienes ya la hayan adquirido (sin pagos adicionales) ni para quienes la adquieran antes del 6 de junio. 👉 Así que, si deseas adquirirl

👍1

28 May 2026, 03:37 UTC509 viewsread 8 August 2026

He recibido muchos mensajes sobre el acceso a los canales de notificaciones. Atendiendo a vuestras peticiones. a partir de ahora: 🗓 Si te interesa tener acceso a los canales de notificaciones, envía un mensaje a @Laurabombis 🤖 Si te interesa convertirte en socio y contratar un servicio de bot para tus clientes, envía un mensaje a @USA_visas

16 May 2026, 03:33 UTC434 viewsread 8 August 2026
Forwarded from @usa_visas_mxPhoto

🙌 Hola a todos! El servicio gratuito de notificaciones ya no está disponible. Creo que ayudó a mucha gente a conseguir citas. Pero a partir de ahora solo estará disponible para socios. Los socios son gerentes y agencias que programan citas utilizando mi bot. Si deseas empezar a programar citas con el bot, envía un mensaje a @USA_visas y hablaremos de los detalles.

Showing the 12 most recent of 20 posts we hold for @usa_visa_tn_mexico. 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 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.

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

“🇲🇽 USA Visa TN Appointments | 🇲🇽 Visado TN Citas Estados Unidos” (@usa_visa_tn_mexico), 544 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/usa_visa_tn_mexico.

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.