388 и 4

Channel
.
@almaty_intimkaz_kyzdar
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
3,061subscribers
+3,013 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002150140300 |
|---|---|
| Type | Channel |
| Username | @almaty_intimkaz_kyzdar |
| Created | 3 July 2024 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 5 times, most recently 2 October 2026 |
| On Telegram | t.me/almaty_intimkaz_kyzdar |
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 14 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 10:06 | 3,061 | -3 |
| 31 Aug 2026, 03:06 | 3,064 | +1 |
| 22 Aug 2026, 15:25 | 3,063 | +3,016 |
| 15 Aug 2026, 02:47 | 47 | -1 |
| 10 Aug 2026, 13:01 | 48 | no change |
| 7 Aug 2026, 13:01 | 48 | first reading |
Engagement
6 posts held, back to 3 July 2024 — 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 6 posts for this entry, the most recent from 2 November 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
.
https://t.me/kazashki_massazh_almaty0
https://t.me/o_tanysulad_intimoty_almatypat https://t.me/gj_kyzdarha_intimono_almatyma https://t.me/Almatyc_almatinky https://t.me/rs_kyzdarpc_almatinkyrf_almatynq https://t.me/rt_kyzdar_almaty https://t.me/gh_kyzdarnet_almatynai_almatinky https://t.me/rv_almaty_kyzdarnet_almatinkyny https://t.me/almatinkies_kyzdarnik_almatinkys https://t.me/bo_intimfge_almatyhu_kyzdaraiki https://t.me/frg_kyzdarhd_almatyjd_almat…
Channel photo updated
Channel created
Showing the 6 most recent of 6 posts we hold for @almaty_intimkaz_kyzdar. 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.
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.
@almatinkies_kyzdarnik_almatinkys · 5,4351 post.
@almatinky_almatinki021 · 5621 post𝘡𝘯𝘢𝘬𝘰𝘮𝘴𝘵𝘷𝘢 𝘬𝘺𝘻𝘥𝘢𝘳 𝘪𝘯𝘵𝘪𝘮𝘴𝘰𝘭 𝘢𝘭𝘮𝘢𝘵𝘪𝘯𝘬𝘺 𝘢𝘭𝘮𝘢𝘵𝘺
@almatinky_znakomstva · 1,1131 postAlmaty feika
@almaty_feika_tanysu · 2381 postKYZDARKI
@almaty_intimko_almatinky · 8,4031 post.
@almaty_intimor · 1371 postKYZDAR ALMATINKY
@almaty_kyzdar_znakomstvap · 1,2031 postАлматы💋знакомства
@almaty_znakomstvap · 6261 postКЫЗДАР АЛМАТЫ АЛМАТИНКИ
@dh_kyzdarvh_almatypu_almatinkydk · 5411 post305
@frg_kyzdarhd_almatyjd_almatinkyr · 2591 post336
@gg_almatyib_intimsjf_tanysufbs · 6,0271 postKyzdarnet almaty
@gh_kyzdarnet_almatynai_almatinky · 3,5361 postКыздар нет Алматы Алматинки
@gj_kyzdarha_intimono_almatyma · 681 postKYZDAR ALMATINKY
@kyzdar_almatinky_almaty2 · 7361 post.
@kyzdar_almaty_z · 751 post289
@kyzdarnet_almatysuo_almatinkyes · 2,4241 post.
@kyzdaruh_almatyso_almatinkyla · 2861 post.
@kyzdarusa_almatinkycool_almatyha · 4551 post.
@kz_intimkoso_kyzdar_massazhzo · 6,6181 postПроститутки Алматы 👑 Эскорт индивидуалки
@o_tanysulad_intimotu_almatypat · 1411 postО KYZDAR
@o_tanysulad_intimoty_almatypat · 22,3941 post8
@rt_kyzdar_almaty · 3,8461 post247
@rv_almaty_kyzdarnet_almatinkyny · 1,4601 post225
@zb_kyzdarnet_almaty_almatinky · 4,8971 post
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“.” (@almaty_intimkaz_kyzdar), 3,061 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/almaty_intimkaz_kyzdar.
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.