Telegram RegisterThe public register of Telegram
Telegram profile photo for Ахуенная Одесса

Channel

Ахуенная Одесса

@axydessa

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Citations · Cite this entry

32,607subscribers

+29,187 since we began measuring on 28 September 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001416850129
TypeChannel
Username@axydessa
DescriptionЛёгкие и позитивные новости одесского региона: без жести, тревог и негатива ⚓️ Прислать новость — @axydessa_bot По рекламе — @xydessa_bot
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 September 2026
Last confirmed live15 November 2026
Measurements held32
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/axydessa

Topic

Local community — 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 13 October 2026 and assigned it the closest of 31 fixed categories, at 76% 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.

Observations

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.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@axydessa/382 · this entry29 Oct 2026, 15:00 UTC@xydessa/7320829 Oct 2026, 18:00 UTC1.003.0 hours
@axydessa/411 · this entry31 Oct 2026, 16:51 UTC@xydessa/7326031 Oct 2026, 17:03 UTC1.0012 minutes
@axydessa/433 · this entry1 Nov 2026, 12:14 UTC@xydessa/732931 Nov 2026, 13:00 UTC1.0046 minutes
@axydessa/446 · this entry2 Nov 2026, 18:02 UTC@xydessa/733623 Nov 2026, 07:03 UTC1.0013 hours
@xydessa/733643 Nov 2026, 08:00 UTC@axydessa/450 · this entry3 Nov 2026, 15:00 UTC1.007.0 hours
@xydessa/7372911 Nov 2026, 13:22 UTC@axydessa/562 · this entry11 Nov 2026, 15:00 UTC1.001.6 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@xydessa6 (6/6 hand-verifiable sample passed)1.003.0 hoursthis entry (4–2)
@xydessa_search5 (5/5 hand-verifiable sample passed)1.006.0 hours@xydessa_search (4–1)

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. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 32 comparable posts for this entry, running 16 October 2026 to 14 November 2026. 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.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @xydessa. That is a statement about our reading window, not a claim of authorship.

Views per post sit far above this size band

33,300 average views per post against 31,363 subscribers — an engagement rate of 106.2%. Across the 21,335 registered channels in the same cohort — 10,000–31,621 subscribers, posting mainly in Russian — the middle half sit between 5.84% and 23.6%, with a median of 12.1%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured105 of 105 published in the window (0 exact, 105 rounded by Telegram)
Views totalled3,498,870
Mature posts only118.7% over 64 posts read at least 24h after publication
Subscribers31,363 measured 5 November 2026
Cohortb10000:rus · 21,335 channels · p10 2.94% · p25 5.84% · p50 12.1% · p75 23.6% · p90 42.5%
Position in cohort99.395th percentile · 8.8× the cohort median
Uncertainty±0.097% of the figure, from Telegram’s rounding
Post languageRussian · 95.2% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_copy · clone_source · err_high, last confirmed 16 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.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.

Growth

3,42032,60718,013.528 September 2026 — 3,420 subscribers5 October 2026 — 11,853 subscribers9 October 2026 — 15,725 subscribers13 October 2026 — 20,689 subscribers14 October 2026 — 22,104 subscribers16 October 2026 — 22,622 subscribers17 October 2026 — 23,516 subscribers18 October 2026 — 24,100 subscribers19 October 2026 — 24,606 subscribers20 October 2026 — 25,152 subscribers21 October 2026 — 25,279 subscribers22 October 2026 — 25,964 subscribers23 October 2026 — 26,457 subscribers24 October 2026 — 26,919 subscribers25 October 2026 — 27,230 subscribers26 October 2026 — 27,308 subscribers27 October 2026 — 28,226 subscribers28 October 2026 — 28,389 subscribers29 October 2026 — 28,731 subscribers30 October 2026 — 28,863 subscribers31 October 2026 — 29,094 subscribers1 November 2026 — 29,240 subscribers2 November 2026 — 29,908 subscribers3 November 2026 — 30,548 subscribers4 November 2026 — 31,292 subscribers5 November 2026 — 31,363 subscribers6 November 2026 — 31,344 subscribers7 November 2026 — 31,360 subscribers8 November 2026 — 31,375 subscribers10 November 2026 — 31,877 subscribers12 November 2026 — 32,369 subscribers15 November 2026 — 32,607 subscribers28 September 202615 November 2026
32 measurements spanning 48 days, net +29,187. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
15 Nov 2026, 18:5032,607+238
12 Nov 2026, 07:5932,369+492
10 Nov 2026, 09:2231,877+502
8 Nov 2026, 20:5831,375+15
7 Nov 2026, 11:3831,360+16
6 Nov 2026, 15:0031,344-19
5 Nov 2026, 11:3931,363+71
4 Nov 2026, 12:3631,292+744
3 Nov 2026, 11:4530,548+640
2 Nov 2026, 10:0529,908+668
1 Nov 2026, 11:4629,240+146
31 Oct 2026, 11:1429,094+231
30 Oct 2026, 11:5528,863+132
29 Oct 2026, 15:0128,731+342
28 Oct 2026, 12:4028,389+163
27 Oct 2026, 12:3528,226+918
26 Oct 2026, 11:4027,308+78
25 Oct 2026, 13:5527,230+311
24 Oct 2026, 12:1626,919+462
23 Oct 2026, 09:1826,457first reading

Engagement

179 posts held, back to 27 September 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 56 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
84.9%
avg views ÷ 32,607 subscribers
Avg views / post
27,700
161 posts measured
Reaction rate
1.09%
reactions ÷ views · ER floor
Posts in window
162
of 179 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 16 November 2026
Posts held179 (27 September 2026 – 16 November 2026)
Views total4,458,734
Reactions total48,732
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 13:12 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
391
Videos
244
Links
272

Lifetime counters from Telegram’s own channel header, read 16 November 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.

Video runtime
48m 09s
Average length
25s

Measured directly from 117 videos 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.

Reaction mix

52,566 reactions across 178 posts, in 8 distinct kinds. The most used accounts for 58.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤30,72158.4%
😁9,86118.8%
🔥5,68410.8%
🤯1,5092.87%
💔1,3832.63%
🎃1,3422.55%
💯1,0952.08%
🙏9711.85%

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

Measured over the 179 most recent posts we hold, published 27 September 2026 to 16 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.

Advertising

Ad load
0.559%
1 of 179 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
14,300
over 1 measured post
Median views · rest
10,800
over 177 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 179 most recent posts we hold, published 27 September 2026 to 16 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 8 of 162 posts held from the last 30 days (4.94%) 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).

16 Nov 2026, 13:07 UTC784 views17 reactionsread 16 November 2026
Video

Кого только не выгуливают в Одессе 🐐 ⚓️ Ахуенная Одесса Прислать новость

❤16😁1

16 Nov 2026, 11:56 UTC≈2,880 views56 reactionsread 16 November 2026

Posted without readable text

❤43🎃5😁5💯2🔥1

16 Nov 2026, 10:07 UTC≈4,950 views203 reactionsread 16 November 2026
Video

Танцы на берегу 👯‍♀ ⚓️ Ахуенная Одесса Прислать новость

❤162🔥27😁9💯3🙏2

16 Nov 2026, 07:07 UTC≈6,600 views209 reactionsread 16 November 2026
Video

А какая Одесса вам больше нравится? ⚓️ Ахуенная Одесса Прислать новость

❤193🙏8😁5🔥2💯1

15 Nov 2026, 19:07 UTC≈8,730 views353 reactionsread 16 November 2026
Video

Саксофон, одесский балкончик и музыка, которая заставляет улыбнуться 🎷✨ ⚓️ Ахуенная Одесса Прислать новость

❤285🔥44🙏13💯7😁3🤯1

15 Nov 2026, 16:07 UTC≈9,070 views396 reactionsread 16 November 2026
Video

И чем мы хуже ? 🗿 ⚓️ Ахуенная Одесса Прислать новость

❤280🔥68💯36💔5🙏4😁2🎃1

15 Nov 2026, 13:07 UTC≈9,610 views188 reactionsread 16 November 2026
Video

🍉 Мини арбузы продаются в Одессе, теперь вы видели всё ⚓️ Ахуенная Одесса Прислать новость

😁117❤56🔥15

15 Nov 2026, 10:07 UTC≈160,000 views340 reactionsread 16 November 2026
Photo

🐈 Новая партия одесских ноябрьских котярышичей ⚓️ Ахуенная Одесса Прислать новость

❤284🔥40😁9💔6🎃1

15 Nov 2026, 07:07 UTC≈10,300 views365 reactionsread 16 November 2026
Video

И пусть весь мир подождёт ☀️ 🌊 ⚓️ Ахуенная Одесса Прислать новость

❤298🔥55💔9😁2💯1

14 Nov 2026, 18:07 UTC≈10,600 views386 reactionsread 16 November 2026
Photo

Одесский аэровокзал - воспоминания 😍 ⚓️ Ахуенная Одесса Прислать новость

❤231💔133💯11🔥4🙏4😁3

14 Nov 2026, 14:53 UTC≈84,900 views196 reactionsread 15 November 2026
Photo

Закат сегодня 🌅 ⚓️ Ахуенная Одесса Прислать новость

❤165🔥31

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

Mentions

Named by 4 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.

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

“Ахуенная Одесса” (@axydessa), 32,607 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/axydessa.

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.