Telegram RegisterThe public register of Telegram
Telegram profile photo for Новости FixMaps

Channel

Новости FixMaps

@FixMapsNews

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

13subscribers

+0 since we began measuring on 10 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004318137405
TypeChannel
Username@FixMapsNews
DescriptionТут короче новости FixMaps Обычный канал: @FixMaps Сотрудничаем с @polisharieoon @newspopsa @NIWAnews
CreatedBetween 1 June 2026 and 10 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/FixMapsNews

Growth

1310 August 2026 — 13 subscribers12 August 2026 — 13 subscribers10 August 202612 August 2026
2 measurements spanning 2 days. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:3113no change
10 Aug 2026, 06:4713first reading

Engagement

20 posts held, back to 10 July 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
235.0%
avg views ÷ 13 subscribers
Avg views / post
30.5
11 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
11
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 July 2026
Posts held20 (10 July 202629 July 2026)
Views total336
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
3
Links
2

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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😇150.0%
🤯150.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 2 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 2reactions 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 10 July 2026 to 29 July 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

29 Jul 2026, 08:22 UTC13 viewsread 12 August 2026

Может комментарии здесь откроем?

Signed 𝗟𝗮𝗿𝗽 𝗯𝗼𝘆

29 Jul 2026, 08:21 UTC6 viewsread 12 August 2026
Forwarded from @FixMaps

ребят какую карту мне нарисовать?

Signed 😮‍💨🧡𝔓𝔯𝔬23𝔨🧡😮‍💨

28 Jul 2026, 15:10 UTC15 viewsread 12 August 2026

короче послезавтра сделаю ещё одну карту

21 Jul 2026, 17:37 UTC42 viewsread 12 August 2026

Короче я щас полностью выгорел и ВОЗМОЖНО я либо продам, либо кому-то передам канал, тока хз кому и за сколько, так что сами предлагайте что делать с каналом Вы типо такие окак😳😳😳🤣😂🤣😂🤣

19 Jul 2026, 18:00 UTC57 viewsread 12 August 2026
Poll

Лан, давайте уже разберёмся, когда и сколько я буду кидать карты?

  1. Каждый день по одной карте44%
  2. Каждые 3 дня по двум картам33%
  3. Каждую неделю по четыре карты6%
  4. Каждые 2 недели по 7 карт17%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

19 Jul 2026, 06:28 UTC27 viewsread 12 August 2026

Штоооо стак подписчиков, спс большое😱😱😱❤️‍🔥❤️‍🔥❤️‍🔥

18 Jul 2026, 21:34 UTC40 viewsread 12 August 2026
Photo

Блять, заняло у меня 2 часа, чтобы нарисовать Евразию, Африку и Океанию. Завтра доделаю, а пока всем спокойной ночи

18 Jul 2026, 18:33 UTC32 viewsread 12 August 2026

Сегодня ВОЗМОЖНО карта, если апатия даст мне

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

19 Jul 2026, 18:00 UTCFinal Results18 voters

Лан, давайте уже разберёмся, когда и сколько я буду кидать карты?

  1. Каждый день по одной карте44%
  2. Каждые 3 дня по двум картам33%
  3. Каждую неделю по четыре карты6%
  4. Каждые 2 недели по 7 карт17%

Shares as published. No per-option vote count is published by Telegram, so none is 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 20 most recent posts we hold, published 10 July 2026 to 29 July 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.

Forward network

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.

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

“Новости FixMaps” (@FixMapsNews), 13 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/FixMapsNews.

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.