Telegram RegisterThe public register of Telegram
Telegram profile photo for (=^・ω・^=) Лотейфик

Channel

(=^・ω・^=) Лотейфик

@Loteyfikk

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

107subscribers

+20 since we began measuring on 3 November 2026

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

Register entry

Telegram ID-1002683499867
TypeChannel
Username@Loteyfikk
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live14 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/Loteyfikk

Growth

87107973 November 2026 — 87 subscribers4 November 2026 — 95 subscribers14 November 2026 — 107 subscribers3 November 202614 November 2026
3 measurements spanning 11 days, net +20. 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 84–110 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 13:38107+12
4 Nov 2026, 22:0695+8
3 Nov 2026, 22:2287first reading

Engagement

11 posts held, back to 31 October 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
289.7%
avg views ÷ 107 subscribers
Avg views / post
310
11 posts measured
Reaction rate
4.90%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 3 November 2026
Posts held11 (31 October 2026 – 3 November 2026)
Views total3,410
Reactions total167
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 22:22 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.

Reaction mix

167 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 25.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52269730775181999064325.7%
custom 53911378816013684293319.8%
custom 54249776969983159982816.8%
custom 52266540860021536212615.6%
custom 52290916603312742802112.6%
custom 5228813415169957874169.58%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 11 of the 11 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 167 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 31 October 2026 to 3 November 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

Telegram’s own ‘edited’ marker: 0 of 11 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 17:04 UTC≈2,290 views17 reactionsread 3 November 2026
Photo

Я ее люблю капец

custom 53911378816013684298custom 52269730775181999065custom 54249776969983159984

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 17:03 UTC156 views14 reactionsread 3 November 2026
Photo

Балдеет булка

custom 52269730775181999067custom 53911378816013684294custom 54249776969983159983

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 16:53 UTC20 views9 reactionsread 3 November 2026
Forwarded from @tamokkkaPhoto

у нас свидание

custom 52269730775181999065custom 53911378816013684292custom 54249776969983159982

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 15:56 UTC26 views11 reactionsread 3 November 2026
Forwarded from @tamokkkaVideo message

Video message, posted without a caption

custom 54249776969983159986custom 53911378816013684293custom 52269730775181999062

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 15:56 UTC26 views8 reactionsread 3 November 2026
Forwarded from @tamokkkaVideo message

Video message, posted without a caption

custom 52269730775181999064custom 52290916603312742802custom 53911378816013684292

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 13:01 UTC145 views18 reactionsread 3 November 2026
Photo

Всем новосибирским салам

custom 52290916603312742808custom 52266540860021536215custom 52269730775181999065

Signed 𝓓𝓲𝓷𝓪

3 Nov 2026, 08:36 UTC143 views17 reactionsread 3 November 2026
Photo

🐱ухожу

custom 52288134151699578746custom 52266540860021536215custom 52290916603312742803custom 52269730775181999062custom 53911378816013684291

Signed 𝓓𝓲𝓷𝓪

1 Nov 2026, 13:22 UTC150 views16 reactionsread 3 November 2026
Photo

Photo, posted without a caption

custom 52269730775181999067custom 53911378816013684295custom 52290916603312742804

Signed 𝓓𝓲𝓷𝓪

1 Nov 2026, 13:16 UTC162 views21 reactionsread 3 November 2026
Photo

наконец-то дошла до граф планшета

custom 52266540860021536219custom 52288134151699578745custom 54249776969983159985custom 53911378816013684292

Signed 𝓓𝓲𝓷𝓪

31 Oct 2026, 17:13 UTC147 views20 reactionsread 3 November 2026
Photo

Хапи халовин 🐱🤩

custom 54249776969983159988custom 52266540860021536217custom 52288134151699578745

Signed 𝓓𝓲𝓷𝓪

31 Oct 2026, 14:02 UTC145 views16 reactionsread 3 November 2026
Photo

До/после 🐱

custom 52269730775181999066custom 53911378816013684296custom 52290916603312742804

Signed 𝓓𝓲𝓷𝓪

Showing the 11 most recent of 11 posts we hold for @Loteyfikk. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“(=^・ω・^=) Лотейфик” (@Loteyfikk), 107 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Loteyfikk.

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.