Telegram RegisterThe public register of Telegram
Telegram profile photo for Битва городов | Дзюдо

Channel

Битва городов | Дзюдо

@judocitiesbattlesochi

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Cite this entry

8,349subscribers

+1,594 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003147945713
TypeChannel
Username@judocitiesbattlesochi
DescriptionОфициальный канал юношеского турнира по дзюдо «Битва городов». ⚡️ Мы в Max: https://max.ru/channel_judobattle ▫️Наш сайт: https://judobattle.com/ ▫️ВК: https://vk.com/judocitiesbattle ▫️TikTok: http://www.tiktok.com/@judocitiesbattle
CreatedBetween 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/judocitiesbattlesochi

Topic

Sports — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 1 other registered channel. 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.

No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.

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
@rus_judo23 (8/8 hand-verifiable sample passed)1.0029 minutesthis entry (22–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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 277 comparable posts for this entry, running 3 August 2026 to 16 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).

Recorded under the key clone_source, last confirmed 17 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.

Growth

6,7558,3497,5526 August 2026 — 6,755 subscribers6 August 2026 — 6,755 subscribers9 August 2026 — 6,804 subscribers12 August 2026 — 6,792 subscribers16 August 2026 — 6,786 subscribers19 August 2026 — 6,776 subscribers22 August 2026 — 6,788 subscribers26 August 2026 — 6,786 subscribers29 August 2026 — 6,782 subscribers1 September 2026 — 6,783 subscribers5 September 2026 — 6,831 subscribers10 September 2026 — 6,859 subscribers13 September 2026 — 6,935 subscribers17 September 2026 — 6,970 subscribers27 September 2026 — 7,155 subscribers5 October 2026 — 7,238 subscribers11 October 2026 — 7,288 subscribers14 October 2026 — 7,321 subscribers17 October 2026 — 7,374 subscribers20 October 2026 — 7,387 subscribers23 October 2026 — 7,459 subscribers26 October 2026 — 7,547 subscribers29 October 2026 — 7,614 subscribers1 November 2026 — 7,605 subscribers4 November 2026 — 7,620 subscribers7 November 2026 — 7,767 subscribers10 November 2026 — 8,160 subscribers15 November 2026 — 8,349 subscribers6 August 202615 November 2026
28 measurements spanning 101 days, net +1,594. 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 6,516–8,588 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
15 Nov 2026, 17:598,349+189
10 Nov 2026, 16:068,160+393
7 Nov 2026, 13:097,767+147
4 Nov 2026, 19:497,620+15
1 Nov 2026, 21:497,605-9
29 Oct 2026, 20:587,614+67
26 Oct 2026, 21:457,547+88
23 Oct 2026, 15:197,459+72
20 Oct 2026, 19:017,387+13
17 Oct 2026, 20:357,374+53
14 Oct 2026, 22:597,321+33
11 Oct 2026, 20:227,288+50
5 Oct 2026, 10:017,238+83
27 Sept 2026, 04:417,155+185
17 Sept 2026, 23:026,970+35
13 Sept 2026, 22:576,935+76
10 Sept 2026, 09:576,859+28
5 Sept 2026, 07:026,831+48
1 Sept 2026, 09:246,783+1
29 Aug 2026, 10:546,782first reading

Engagement

346 posts held, back to 3 August 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 42 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
18.2%
avg views ÷ 8,349 subscribers
Avg views / post
1,520
311 posts measured
Reaction rate
0.715%
reactions ÷ views · ER floor
Posts in window
311
of 346 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. It is computed over the 264 of 311 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held346 (3 August 2026 – 17 November 2026)
Views total473,404
Reactions total3,038
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 03:06 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
≈1,440
Videos
≈1,800
Links
≈2,520

Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1h 40m
Average length
28s

Measured directly from 215 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

4,915 reactions across 286 posts, in 25 distinct kinds. The most used accounts for 49.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,45149.9%
🔥94219.2%
custom 53979725962034629164669.48%
👍2294.66%
😍2214.50%
❤‍🔥1272.58%
🤩1032.10%
🏆671.36%
👏551.12%
💘521.06%
😢521.06%
💋340.692%
😭210.427%
💯180.366%
😁160.326%
🥰110.224%
🤔100.203%
👀90.183%
🤪90.183%
⚡80.163%
5 further kinds140.285%

Custom emoji. One 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 count beside it is 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 299 of the 346 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 4,915 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 346 most recent posts we hold, published 3 August 2026 to 17 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.

Telegram Stars

Stars received
106
across the posts below
Posts paid on
22
of 346 we hold a reading for · 6%
Most on one post
20
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @judocitiesbattlesochi. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 346 most recent posts we hold for this entry, published 3 August 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

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

17 Nov 2026, 18:36 UTC≈1,170 views22 reactionsread 18 November 2026
Photo

⚡️ Кто возглавил рейтинг участников Суперфинала «Битвы Городов»? 16 команд завоевали путёвки в Международный Суперфинал, стали частью рейтинга чемпионов легионов. Итоговая позиция команды сформирована с учётом результатов всех этапов турнира — от первых отборочных встреч до Гранд Финала, в котором сошлись восемь победителей легионов. 🏆 По итогам турнира первую строчку занимает «Фрязино» с результатом +114 В тройке…

🔥16❤6

17 Nov 2026, 16:14 UTC≈1,380 views7 reactionsread 18 November 2026
Video

🎙 От Липецка — к мировому татами : «ALEX» и «Rodioncshik» о целях в спорте! Два месяца усердной подготовки — и большие цели впереди: U15, U18 и международные старты. 🥋 Ребята занимаются дзюдо с детства и мечтают выполнить мастера спорта, выступить на чемпионате мира и однажды отобраться на Олимпиаду. #БитваГородов 📲 Битва Городов в МАХ

❤7

17 Nov 2026, 12:46 UTC≈1,610 views13 reactionsread 18 November 2026
Video

⚡️Интервью с победителем Младшего Дивизиона U15! Тигран «Tiger» из команды «Химки» рассказал, как прошли встречи на «Битве Городов», поделился эмоциями от первого места в подгруппе и назвал свои главные цели в дзюдо. Ставьте 🔥, если болеете за команду «Химки» на турнире. #БитваГородов 📲 Битва Городов в МАХ

🔥7❤6

17 Nov 2026, 09:56 UTC≈1,640 views16 reactionsread 18 November 2026
Video

⚡️Вспомним, как прошёл Высший дивизион «Битвы Городов» в Москве! С 26 по 28 октября команды сражались на татами за выход в следующий этап «Битвы Городов». Собрали для вас самые яркие моменты встреч в Легионе Кутузова. 🎥 Смотрите видео с соревнований в официальном канале Битвы Городов во ВКонтакте #БитваГородов 📲 Битва Городов в МАХ

❤9🔥5custom 53979725962034629162

16 Nov 2026, 13:34 UTC≈1,850 views6 reactionsread 18 November 2026
Video

🔜Кузьмин Тихон «УДАВ» — о командной победе🔚 В дзюдо Тихон уже 8 лет. В этот спорт его привёл отец, который сам много лет занимался дзюдо и добился серьёзных результатов. Одна из главных целей самого Тихона — стать мастером спорта международного класса. #БитваГородов 📲 Битва Городов в МАХ

❤6

16 Nov 2026, 11:05 UTC≈1,860 views9 reactionsread 18 November 2026
Video

🏆 Церемония награждения команд Высшего дивизиона! Медали, эмоции и заслуженные аплодисменты — смотрите яркие моменты второго этапа «Битвы Городов». #БитваГородов 📲 Битва Городов в МАХ

❤7👍2

16 Nov 2026, 06:55 UTC≈1,930 views73 reactionsread 18 November 2026
Video

🎙 Голос Гранд Финала «Битвы городов» — Евгений Моспанов Именно он помогает проживать каждую схватку ещё ярче! Ставь ❤️ работе комментатора! #БитваГородов

❤56🔥13🏆4

15 Nov 2026, 16:57 UTC≈1,990 views13 reactions3 Starsread 18 November 2026
Video

🎙Александр Огнев — «ЛЕВ»,«Липецк» Эмоции после встречи — только положительные. Команда «Липецк» одержала победу над «Уфой», а Александр завершил свою схватку броском и удержанием. В дзюдо Александра привела мама, которая сама занималась этим видом спорта. По его словам, дзюдо дало ему дисциплину и терпение. #БитваГородов 📲 Битва Городов в МАХ

❤11❤‍🔥1👍1

15 Nov 2026, 14:37 UTC≈1,980 views12 reactions1 Starread 18 November 2026
Video

💬Давид Мхитарян — «DAVID»,«Химки» Для Давида «Битва Городов» стала новым и очень мотивирующим опытом. 🥋 В дзюдо Давид уже 8 лет. В спорт он пришёл по собственному желанию и почти сразу понял: это именно его путь. После турнира Давид выделил ошибки, над которыми будет работать дальше. 📲 Битва Городов в МАХ

❤10❤‍🔥1🔥1

15 Nov 2026, 13:09 UTC≈2,020 views19 reactions19 Starsread 18 November 2026
Video

☄️ Тимур «Khabareli» — капитан команды «Москва» в младшем дивизионе U15! Спортсмен поделился эмоциями от турнира, рассказал о роли капитана и планах на будущее в дзюдо. Ставьте «❤️», если болели за команду «Москва» #БитваГородов 📲 Битва Городов в МАХ

❤15🔥3💘1

15 Nov 2026, 10:40 UTC≈2,050 views9 reactions5 Starsread 18 November 2026
Video

🎙Мамед Гезалов — «HURRICANE», команда «Москва» Мамед отмечает, что именно тренер помог ему поставить технику и дал прочную базу в дзюдо. Отдельные слова благодарности — болельщикам за поддержку и атмосферу на трибунах 🙌 🎯 Главная цель на «Битве Городов» — отобраться на следующий этап вместе со старшим годом. #БитваГородов 📲 Битва Городов в МАХ

❤8🔥1

15 Nov 2026, 08:12 UTC≈2,220 views11 reactionsread 18 November 2026
Photo

🇷🇺Команда «Химки» побеждает на международном этапе в Белграде и выходит в Суперфинал! 11 ноября в столице Сербии прошёл этап Континентального дивизиона «Битвы Городов». Дзюдоисты из «Химок» одержали три победы в трёх встречах, заняли первое место с разницей +26 и завоевали путёвку в Международный Суперфинал. 🥈 Второе место — «Белград» 🥉 Третье место — «Нови-Сад» Все подробности этапа читайте на сайте Битвы Городо…

❤9🔥2

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@judocitiesbattlesochi edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
4 November 2026
Most recent edit
16 November 2026

Polls

The 6 most recent of 33 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Nov 2026, 15:39 UTCAnonymous Poll238 voters

За какую команду болеете?

  1. ✅Химки91%
  2. ✅Белград13%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

11 Nov 2026, 14:30 UTCAnonymous Poll104 voters

Какую команду поддерживаете?

  1. ☄️Селенгинск70%
  2. ☄️Нови Сад34%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

11 Nov 2026, 12:30 UTCAnonymous Poll179 voters

Кого поддерживаете?

  1. ⚡️Химки94%
  2. 🔥Нови-Сад7%

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

11 Nov 2026, 10:47 UTCAnonymous Poll130 voters

Какую команду поддерживаете?

  1. ⚡️Селенгинск43%
  2. ⚡️Белград62%

The shares total 105%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

11 Nov 2026, 07:49 UTCAnonymous Poll211 voters

Какую команду поддерживаете?

  1. 🇷🇺Селенгинск13%
  2. 🇷🇺Химки89%

The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

10 Nov 2026, 15:13 UTCAnonymous Poll396 voters

🥋 Кто же станет победителем Гранд Финала? #БитваГородов

  1. ⚡️ Фрязино67%
  2. 🔥 Назрань33%

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 346 most recent posts we hold, published 3 August 2026 to 17 November 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.

Mentions

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

“Битва городов | Дзюдо” (@judocitiesbattlesochi), 8,349 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/judocitiesbattlesochi.

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.