Russia recorded 22900755 Coronavirus Cases since the epidemic began, according to the World Health Organization (WHO). In addition, Russia reported 398736 Coronavirus Deaths. This dataset includes a chart with historical data for Russia Coronavirus Cases.

COVID-19 in Russia was centered in the city of Moscow, which accounted for the highest number of cases, measuring at around 3.5 million as of June 4, 2023. It was followed by Saint Petersburg with more than 1.9 million cases. In total, over 22.9 million COVID-19 cases were recorded in Russia as of June 4, 2023.

COVID-19 in Moscow The city of Moscow was Russia’s region with the largest number of conducted COVID-19 tests. Moscow's self-isolation index during the lockdown indicated that most residents stayed home. With entertainment venues, restaurants and bars, and non-food shops closed, the subway traffic in the capital decreased by 85 percent compared to the previous year. Furthermore, car sharing services were suspended in the city due to risks of the COVID-19 contagion. Until the end of 2021, pensioners in Moscow could receive 10 thousand Russian rubles for getting vaccinated.

Self-isolation regime Due to the COVID-19 outbreak, Russia announced a non-working period until May 11, 2020. Its regions, or federal subjects, imposed additional quarantine measures to restrict movement of residents and transport during the shutdown. In most regions, the population could go outside only to the nearest grocery store, to walk a dog, or to see a doctor in emergency cases. Moscow authorities introduced digital passes, requiring Russians to register online before leaving home. Another lockdown was held from the end of October to the beginning of November. For further information about the coronavirus (COVID-19) pandemic, please visit our dedicated Facts and Figures page.

Official Russian COVID-19 data published on a daily basis by the Government of Russia (on the Russian language) in the form of raw data is a daily updated report in a pdf form. Each report has daily updates. We are providing a working link on every cell of data in the dataset. This is an attempt to manually collect key variables from the report into a machine-readable format. These datasets are ready to be used for the analyses and modeling. COVID-19 Datasets is Based on a report on the current situation against coronavirus by the Communicational center of Government of the Russian Federation. Accessed on May 14.2020

Variables: location; date; new cases [diagnosed]; cases [cumulative]; recovered [new]; recovered [cumulative]; deaths [new]; deaths [cumulative]; tests [new tests administered]; tests [cumulative]; test_positive [cumulative]; hospitalization [cumulative]; icu [cumulative or population]; on_invasive_ventilators [cumulative or population]; test_negative [cumulative]; hospital beds; web links.

Dividing by date (time) and regions (Oblast) of the Russian Federation

IMPORTANT (02-Apr-2024)

Kaggle has fixed the issue with gzip files and Version 510 should now reflect properly working files

IMPORTANT (28-Mar-2024)

Please use the version 508 of the dataset, as 509 is broken. See link below of the dataset that is properly working https://www.kaggle.com/datasets/bwandowando/ukraine-russian-crisis-twitter-dataset-1-2-m-rows/versions/508

Context

The context and history of the current ongoing conflict can be found https://en.wikipedia.org/wiki/2022_Russian_invasion_of_Ukraine.

Announcement

[Jun 16] (🌇Sunset) Twitter has finally pulled the plug on all of my remaining TWITTER API accounts as part of their efforts for developers to migrate to the new API. The last tweets that I pulled was dated last Jun 14, and no more data from Jun 15 onwards. It was fun til it lasted and I hope that this dataset was able and will continue to help a lot. I'll just leave the dataset here for future download and reference. Thank you all!

[Apr 19] Two additional developer accounts have been permanently suspended, expect a lower throughtput in the next few weeks. I will pull data til they ban my last account.

[Apr 08] I woke up this morning and saw that Twitter has banned/ permanently suspended 4 of my developer accounts, I have around a few more but it is just a matter of time till all my accounts will most likely get banned as well. This was a fun project that I maintained for as long as I can. I will pull data til my last account gets banned.

[Feb 26] I've started to pull in RETWEETS again, so I am expecting a significant amount of throughput in tweets again on top of the dedicated processes that I have that gets NONRETWEETS. If you don't want RETWEETS, just filter them out.

[Feb 24] It's been a year since I started getting tweets of this conflict and had no idea that a year later this is still ongoing. Almost everyone assumed that Ukraine will crumble in a matter of days, but it is not the case. To those who have been using my dataset, i hope that I am helping all of you in one way or another. Ill do my best to maintain updating this dataset as long as I can.

[Feb 02] I seem to be getting less tweets as my crawlers are getting throttled, i used to get 2500 tweets per 15 mins but around 2-3 of my crawlers are getting throttling limit errors. There may be some kind of update that Twitter has done about rate limits or something similar. Will try to find ways to increase the throughput again.

[Jan 02] For all new datasets, it will now be prefixed by a year, so for Jan 01, 2023, it will be 20230101_XXXX.

[Dec 28] For those looking for a cleaned version of my dataset, with the retweets removed from before Aug 08, here is a dataset by @@vbmokin https://www.kaggle.com/datasets/vbmokin/russian-invasion-ukraine-without-retweets

[Nov 19] I noticed that one of my developer accounts, which ISNT TWEETING ANYTHING and just pulling data out of twitter has been permanently banned by Twitter.com, thus the decrease of unique tweets. I will try to come up with a solution to increase my throughput and signup for a new developer account.

[Oct 19] I just noticed that this dataset is finally "GOLD", after roughly seven months since I first uploaded my gzipped csv files.

[Oct 11] Sudden spike in number of tweets revolving around most recent development(s) about the Kerch Bridge explosion and the response from Russia.

[Aug 19- IMPORTANT] I raised the missing dataset issue to Kaggle team and they confirmed it was a bug brought by a ReactJs upgrade, the conversation and details can be seen here https://www.kaggle.com/discussions/product-feedback/345915 . It has been fixed already and I've reuploaded all the gzipped files that were lost PLUS the new files that were generated AFTER the issue was identified.

[Aug 17] Seems the latest version of my dataset lost around 100+ files, good thing this dataset is versioned so one can just go back to the previous version(s) and download them. Version 188 HAS ALL THE LOST FILES, I wont be reuploading all datasets as it will be tedious and I've deleted them already in my local and I only store the latest 2-3 days.

[Aug 10] 3/5 of my Python processes errored out and resulted to around 10-12 hours of NO data gathering for those processes thus the sharp decrease of tweets for Aug 09 dataset. I've applied an exception/ error checking to prevent this from happening.

[Aug 09] Significant drop in tweets extracted, but I am now getting ORIGINAL/ NON-RETWEETS.

[Aug 08] I've noticed that I had a spike of Tweets extracted, but they are literally thousands of retweets of a single original tweet. I also noticed that my crawlers seem to deviate because of this tactic being used by some Twitter users where they flood Twitter w...

About this dataset

Context

The dataset tabulates the Russia population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Russia.

Content

The dataset will have the following datasets when applicable

Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)

• Russia, OH Population Breakdown by Race
• Russia, OH Non-Hispanic Population Breakdown by Race
• Russia, OH Hispanic or Latino Population Distribution by Their Ancestries

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

I collected the quantitative data from online archives of the four Russian-language media outlets: TASS (https://tass.ru/), Rossiyskaya Gazeta (https://rg.ru/), RIA Novosti (https://ria.ru/), and Lenta.ru (https://lenta.ru/). In each case, I used the Russian-language interface and the Search function of the respective websites. The data were selected manually (without any software) and inserted into Excel spreadsheets, forming four datasets: TASS (Dataset_TASS.xlsx), Rossiyskaya Gazeta (Dataset_ Rossiyskaya_Gazeta.xlsx), RIA Novosti (Dataset_ RIA_Novosti.xlsx), and Lenta.ru (Dataset_Lenta.ru.xlsx). All datasets contain publication date of reports and respective URL (with the exception of Dataset_ RIA_Novosti.xlsx which contains hyperlinks). In each dataset, the reports containing attribution of cyberattacks against Russia are highlighted in yellow. These reports are cited and analyzed in greater detail in the “Public Attribution of Cyberattacks in Russia: Longitudinal Media Analysis” section of my paper.

About this dataset

Context

The dataset tabulates the Russia township population by race and ethnicity. The dataset can be utilized to understand the racial distribution of Russia township.

Content

The dataset will have the following datasets when applicable

Please note that in case when either of Hispanic or Non-Hispanic population doesnt exist, the respective dataset will not be available (as there will not be a population subset applicable for the same)

• Russia Township, Minnesota Population Breakdown by Race
• Russia Township, Minnesota Non-Hispanic Population Breakdown by Race
• Russia Township, Minnesota Hispanic or Latino Population Distribution by Their Ancestries

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

We used the Twitter API (V2) to collect all tweets, retweets, quotes and replies containing case-insensitive versions of the hashtags: #(I)StandWithPutin, #(I)StandWithRussia, #(I)SupportRussia, #(I)StandWithUkraine, #(I)StandWithZelenskyy and #(I)SupportUkraine. These were obtained from February 23rd 2022 00:00:00 UTC until March 8th 2022 23:59:59 UTC, the fortnight after Russia invaded Ukraine. We queried the hashtags with and without the `I', a total of 12 query hashtags, collecting 5,203,746 tweets. The data collected predates the beginning of the Russian invasion by one day. These hashtags were chosen as they were found to be the most trending hashtags related to the Russia/Ukraine war which could be easily identified with a particular side in the conflict. We calculated Botometer results on 483,100 (26.5%) of accounts. These accounts were randomly sampled from a list of all unique users in our dataset which posted in English. This random sample leads to an approximately uniform frequency of Tweets from accounts with Botometer labels across the time frame we considered. We include the language dependent and language independent results from Botometer, including the Complete Automation Probabilities (CAP) and each of the sub-category scores for different bot types. Moreoever, we include the display scores and raw scores from Botometer for each account. More information about the Botometer scores can be found at this link: https://rapidapi.com/OSoMe/api/botometer-pro/details You can find our paper here: https://arxiv.org/abs/2208.07038