Facebook
TwitterThis dataset is designed for research on audio deepfake detection, focusing specifically on generated speech in Russian. It contains TTS-generated audio, paired with transcriptions, and a mixed set for real vs fake classification tasks.
The main goal is to support research on audio deepfake detection in underrepresented languages, especially Russian. The dataset simulates real-world scenarios using multiple state-of-the-art TTS systems to generate fakes and includes clean, real audio data.
We used three high-quality TTS models to synthesize Russian speech:
XTTS-v2: Cross-lingual, zero-shot voice cloning with multilingual support.
Silero TTS: Lightweight, real-time Russian TTS model.
VITS RU Multispeaker: VITS-based Russian model with speaker variability.
For real human speech, we used a part of SOVA dataset, which contains clean Russian utterances recorded by multiple speakers.
Facebook
TwitterNew Russian dataset for ELQ (Entity Linking for Questions) model (https://github.com/facebookresearch/BLINK/tree/main/elq)
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Kyrgyz comments are still new things to examine. Defining whether comment is toxic or not is a big challenge. We used YouTube API to get comments. Code can be found here - https://github.com/abdulra7ma/ycc
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
WikiConv (Russian): A Corpus of the Complete Conversational History of a Large Online Collaborative CommunityThis directory contains the WikiConv Corpus which encompasses the full history of conversations on Wikipedia Talk Pages.The project webpage for this work is at: https://github.com/conversationai/wikidetox/tree/master/wikiconvThe dataset and reconstruction process for this corpus has been published in the paper WikiConv: A Corpus of the Complete Conversational History of a Large OnlineCollaborative Community, presented at EMNLP 2018.The work has also been presented at the June 2018 Wikipedia researchshowcase (the first half describes our work, using an earlier version of this dataset to predict conversations going awry.The meta-data in this corpus is governed by the CC0 license v1.0, and the content of the comments is governed by the CC-SA license v3.0.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The texts in the sah column were generated using OCR and may contain errors or artifacts. Please take this into account when using the data for training or evaluation. The dataset was aligned using the Lingtrain Aligner library (https://github.com/averkij/lingtrain-aligner), created by @averoo
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Russian Open Speech To Text (STT/ASR) Dataset Arguably the largest public Russian STT dataset up to date.
Facebook
TwitterThe Russian Financial Statements Database (RFSD) is an open, harmonized collection of annual unconsolidated financial statements of the universe of Russian firms: - 🔓 First open data set with information on every active firm in Russia. - 🗂️ First open financial statements data set that includes non-filing firms. - 🏛️ Sourced from two official data providers: the Rosstat and the Federal Tax Service. - 📅 Covers 2011-2024, will be continuously updated. - 🏗️ Restores as much data as possible through non-invasive data imputation, statement articulation, and harmonization. The RFSD is hosted on 🤗 Hugging Face and Zenodo and is stored in a structured, column-oriented, compressed binary format Apache Parquet with yearly partitioning scheme, enabling end users to query only variables of interest at scale. The accompanying paper provides internal and external validation of the data: https://doi.org/10.1038/s41597-025-05150-1. Here we present the instructions for importing the data in R or Python environment. Please consult with the project repository for more information: http://github.com/irlcode/RFSD. Importing the Data You have two options to ingest the data: download the .parquet files manually from Hugging Face or Zenodo or rely on 🤗 Hugging Face Datasets library. Python 🤗 Hugging Face Datasets It is as easy as: from datasets import load_dataset import polars as pl # This line will download 6.6 GB+ of all RFSD data and store it in a 🤗 cache folder RFSD = load_dataset('irlspbru/RFSD') # Alternatively, this will download ~540 MB with all financial statements for 2023# to a Polars DataFrame (requires about 8 GB of RAM) RFSD_2023 = pl.read_parquet('hf://datasets/irlspbru/RFSD/RFSD/year=2023/*.parquet') Please note that the data is not shuffled within year, meaning that streaming the first n rows will not yield a random sample. Local File Import Importing in Python requires pyarrow package installed. import pyarrow.dataset as ds import polars as pl # Read RFSD metadata from local file RFSD = ds.dataset("local/path/to/RFSD", partitioning="hive") # Use RFSD_dataset.schema to glimpse the data structure and columns' classes print(RFSD.schema) # Load full dataset into memory RFSD_full = pl.from_arrow(RFSD.to_table()) # Load only 2019 data into memory RFSD_2019 = pl.from_arrow(RFSD.to_table(filter=ds.field('year') == 2019)) # Load only revenue for firms in 2019, identified by taxpayer id RFSD_2019_revenue = pl.from_arrow( RFSD.to_table( filter=ds.field('year') == 2019, columns=['inn', 'line_2110'] ) ) # Give suggested descriptive names to variables renaming_df = pl.read_csv('local/path/to/descriptive_names_dict.csv') RFSD_full = RFSD_full.rename({item[0]: item[1] for item in zip(renaming_df['original'], renaming_df['descriptive'])}) R Local File Import Importing in R requires arrow package installed. library(arrow) library(data.table) # Read RFSD metadata from local file RFSD <- open_dataset("local/path/to/RFSD") # Use schema() to glimpse into the data structure and column classes schema(RFSD) # Load full dataset into memory scanner <- Scanner$create(RFSD) RFSD_full <- as.data.table(scanner$ToTable()) # Load only 2019 data into memory scan_builder <- RFSD$NewScan() scan_builder$Filter(Expression$field_ref("year") == 2019) scanner <- scan_builder$Finish() RFSD_2019 <- as.data.table(scanner$ToTable()) # Load only revenue for firms in 2019, identified by taxpayer id scan_builder <- RFSD$NewScan() scan_builder$Filter(Expression$field_ref("year") == 2019) scan_builder$Project(cols = c("inn", "line_2110")) scanner <- scan_builder$Finish() RFSD_2019_revenue <- as.data.table(scanner$ToTable()) # Give suggested descriptive names to variables renaming_dt <- fread("local/path/to/descriptive_names_dict.csv") setnames(RFSD_full, old = renaming_dt$original, new = renaming_dt$descriptive) Use Cases 🌍 For macroeconomists: Replication of a Bank of Russia study of the cost channel of monetary policy in Russia by Mogiliat et al. (2024) — interest_payments.md 🏭 For IO: Replication of the total factor productivity estimation by Kaukin and Zhemkova (2023) — tfp.md 🗺️ For economic geographers: A novel model-less house-level GDP spatialization that capitalizes on geocoding of firm addresses — spatialization.md FAQ Why should I use this data instead of Interfax's SPARK, Moody's Ruslana, or Kontur's Focus?hat is the data period? To the best of our knowledge, the RFSD is the only open data set with up-to-date financial statements of Russian companies published under a permissive licence. Apart from being free-to-use, the RFSD benefits from data harmonization and error detection procedures unavailable in commercial sources. Finally, the data can be easily ingested in any statistical package with minimal effort. What is the data period? We provide financials for Russian firms in 2011-2024. We will add the data for 2025 by July, 2026 (see Version and Update Policy below). Why are there no data for firm X in year Y? Although the RFSD strives to be an all-encompassing database of financial statements, end users will encounter data gaps: We do not include financials for firms that we considered ineligible to submit financial statements to the Rosstat/Federal Tax Service by law: financial, religious, or state organizations (state-owned commercial firms are still in the data). Eligible firms may enjoy the right not to disclose under certain conditions. For instance, Gazprom did not file in 2022 and we had to impute its 2022 data from 2023 filings. Sibur filed only in 2023, Novatek — in 2020 and 2021. Commercial data providers such as Interfax's SPARK enjoy dedicated access to the Federal Tax Service data and therefore are able source this information elsewhere. Firm may have submitted its annual statement but, according to the Uniform State Register of Legal Entities (EGRUL), it was not active in this year. We remove those filings. Why is the geolocation of firm X incorrect? We use Nominatim to geocode structured addresses of incorporation of legal entities from the EGRUL. There may be errors in the original addresses that prevent us from geocoding firms to a particular house. Gazprom, for instance, is geocoded up to a house level in 2014 and 2021-2024, but only at street level for 2015-2020 due to improper handling of the house number by Nominatim. In that case we have fallen back to street-level geocoding. Additionally, streets in different districts of one city may share identical names. We have ignored those problems in our geocoding and invite your submissions. Finally, address of incorporation may not correspond with plant locations. For instance, Rosneft has 62 field offices in addition to the central office in Moscow. We ignore the location of such offices in our geocoding, but subsidiaries set up as separate legal entities are still geocoded. Why is the data for firm X different from https://bo.nalog.ru/? Many firms submit correcting statements after the initial filing. While we have downloaded the data way past the April 1, 2025 deadline for 2024 filings, firms may have kept submitting the correcting statements. We will capture them in the future releases. Why is the data for firm X unrealistic? We provide the source data as is, with minimal changes. Consider a relatively unknown LLC Banknota. It reported 3.7 trillion rubles in revenue in 2023, or 2% of Russia's GDP. This is obviously an outlier firm with unrealistic financials. We have manually reviewed the data and flagged such firms for user consideration (variable outlier), keeping the source data intact. Why is the data for groups of companies different from their IFRS statements? We should stress that we provide unconsolidated financial statements filed according to the Russian accounting standards, meaning that it would be wrong to infer financials for corporate groups with this data. Gazprom, for instance, had over 800 affiliated entities and to study this corporate group in its entirety it is not enough to consider financials of the parent company. Why is the data not in CSV? The data is provided in Apache Parquet format. This is a structured, column-oriented, compressed binary format allowing for conditional subsetting of columns and rows. In other words, you can easily query financials of companies of interest, keeping only variables of interest in memory, greatly reducing data footprint. Version and Update Policy Version (SemVer): 2.0.3. We intend to update the RFSD annualy as the data becomes available, in other words when most of the firms have their statements filed with the Federal Tax Service. The official deadline for filing of previous year statements is April, 1. However, every year a portion of firms either fails to meet the deadline or submits corrections afterwards. Filing continues up to the very end of the year but after the end of April this stream quickly thins out. Nevertheless, there is obviously a trade-off between minimization of data completeness and version availability. We find it a reasonable compromise to query new data in early June, since on average by the end of May 96.7% statements are already filed, including 86.4% of all the correcting filings. We plan to make a new version of RFSD available by late July - early August. Changelog All notable changes to this project will be documented below. The format is based on Keep a Changelog. [2.0.3] - 2025-09-12 Fixed Added previously missing okopf, okfc, and okpo values for new firms entering in 2024. Changed Improved okopf completeness: previously the data on this classification code came only from the Rosstat's Statistical Register of Economic Entities whereas now it is sourced from the Federal Tax Service's EGRUL and GIR BO filings (with EGRUL taking precedence). As a result, we were able to fill missing okopf for <1% of firms, futher slightly improving eligible classification. Impovements in eligibility classification prompted by reduction okopf missingness
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Russian Election Data: data (.csv, .rds) and codebook. Replication material are available at: https://github.com/georgytarasenko/RED-replication-package
Facebook
Twitterhttp://www.gnu.org/licenses/lgpl-3.0.htmlhttp://www.gnu.org/licenses/lgpl-3.0.html
Time series data about COVID-19 situation in Russia
The latest data available in the github repository.
Facebook
TwitterGolos is a Russian corpus suitable for speech research. The dataset mainly consists of recorded audio files manually annotated on the crowd-sourcing platform. The total duration of the audio is about 1240 hours. We have made the corpus freely available for downloading, along with the acoustic model prepared on this corpus. Also we create 3-gram KenLM language model using an open Common Crawl corpus. The main project page: Golos GitHub repository. Check License file en_us.pdf
Facebook
TwitterRussian Military Aircraft in Satellite Imagery
This is the data for the aircraft-classification project. That project detects and classifies Russian military aircraft in satellite images of airbases. It contains:
real images derived from a public Kaggle dataset artificial images generated by placing aircraft cut-outs onto empty airbase images the assets used to generate the artificial images
The layout of this repository matches the data/ directory of the GitHub project. To… See the full description on the dataset page: https://huggingface.co/datasets/BohdanZasymovych/aircraft-classification.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The set of over 2,250 files archived here comprises a database of the Russian Constructicon, an open-access electronic resource freely available at https://constructicon.github.io/russian/. The Russian Constructicon is a searchable database of constructions accompanied with thorough descriptions of their properties and annotated illustrative examples.
Facebook
TwitterImage Caprioning for Russian language
This dataset is a Russian part of dinhanhx/crossmodal-3600
Dataset Details
3.11k rows. Two description for each picture. Cracked pictures were deleted from the original source. The main feature is that all the descriptions are written by the native russian speakers.
Paper [https://google.github.io/crossmodal-3600/]
Uses
It is intended to be used for fine-tuning image captioning models.
Facebook
TwitterThis dataset contains daily geospatial data of Russian-occupied areas in Ukraine, automatically extracted from the open-source DeepStateMap project. The dataset is generated using a Python-based pipeline and updated daily via GitHub Actions.
The data includes:
Daily GeoJSON-based snapshots of territorial control Centroid coordinates and area for each polygonal zone Polygon geometries in WKT (Well-Known Text) format Cleaned, structured, and aggregated into a single CSV for ease of use
This dataset is intended for:
Open-source intelligence (OSINT) workflows Conflict zone mapping and territorial change analysis Machine learning model training on spatial or temporal patterns Geospatial dashboards and time series visualizations
The full data processing pipeline and automation scripts are openly available on GitHub: https://github.com/lazar-bit/deepstate-map-data-analytics
Facebook
Twitterhttps://creativecommons.org/publicdomain/zero/1.0/https://creativecommons.org/publicdomain/zero/1.0/
By [source]
This dataset consists of tweets relating to the Russian invasion of Ukraine that were scraped for this study. Only tweets of which user features were available are included in the dataset. The tweets and corresponding user features can be rehydrated using the Twitter API. However, it could be that some tweets or users might be deleted or put on private and are therefore no longer available. Moreover, user and tweet features might change over time
For more datasets, click here.
- 🚨 Your notebook can be here! 🚨!
The dataset consists of tweets relating to the Russian invasion of Ukraine that were scraped for this study. Only tweets of which user features were available are included in the dataset. The tweets and corresponding user features can be rehydrated using the Twitter API. However, it could be that some tweets or users might be deleted or put on private and are therefore no longer available. Moreover, user and tweet features might change over time This dataset can be used to study the change in sentiment, and topics over time as the war continues
- Find out which tweets are most popular among people interested in the Russian invasion of Ukraine
- Identify which user attributes are associated with tweets about the Russian invasion of Ukraine
- Study the change in sentiment and public opinion on the war as events unfold.
If you use this dataset in your research, please credit the original authors. Data Source
License: CC0 1.0 Universal (CC0 1.0) - Public Domain Dedication No Copyright - You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission. See Other Information.
File: after_invasion_tweetids.csv | Column name | Description | |:--------------|:-----------------------| | id | The tweet id. (String) |
File: before_invasion_tweetids.csv | Column name | Description | |:--------------|:-----------------------| | id | The tweet id. (String) |
If you use this dataset in your research, please credit the original authors. If you use this dataset in your research, please credit .
Facebook
Twitterhttps://academictorrents.com/nolicensespecifiedhttps://academictorrents.com/nolicensespecified
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The repository contains an ongoing collection of tweets IDs associated with the current conflict in Ukraine and Russia, which we commenced collecting on Februrary 22, 2022. To comply with Twitter’s Terms of Service, we are only publicly releasing the Tweet IDs of the collected Tweets. The data is released for non-commercial research use. Note that the compressed files must be first uncompressed in order to use included scripts. This dataset is release v1.3 and is not actively maintained -- the actively maintained dataset can be found here: https://github.com/echen102/ukraine-russia. This release contains Tweet IDs collected from 2/22/22 - 1/08/23. Please refer to the README for more details regarding data, data organization and data usage agreement. This dataset is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License . By using this dataset, you agree to abide by the stipulations in the license, remain in compliance with Twitter’s Terms of Service, and cite the following manuscript: Emily Chen and Emilio Ferrara. 2022. Tweets in Time of Conflict: A Public Dataset Tracking the Twitter Discourse on the War Between Ukraine and Russia. arXiv:cs.SI/2203.07488
Facebook
TwitterBackground The association between the human cytotoxic T lymphocyte-associated antigen-4 (CTLA4) gene and insulin-dependent diabetes mellitus (IDDM) is unclear in populations. We therefore investigated whether the gene conferred susceptibility to IDDM in a Russian population. We studied two polymorphic regions of the CTLA4 gene, the codon 17 dimorphism and the (AT)n microsatellite marker in the 3' untranslated region in 56 discordant sibling pairs and in 33 identical by descent (IBD) affected sibships.
Results
The Ala17 allele of the CTLA4 gene was preferentially transmitted from parents to diabetic offspring (p < 0.0001) as shown by the combined transmission/disequlibrium test (TDT) and sib TDT (S-TDT) analysis. A significant difference between diabetic and non-diabetic offspring was also observed for the transmission of alleles 17, 20, and 26 of the dinucleotide microsatellite. Allele 17 was transmitted significantly more frequently to affected offspring than to other children (p = 0.0112) whereas alleles 20 and 26 were transmitted preferentially to non-diabetic sibs (p = 0.045 and 0.00068 respectively). A nonrandom excess of the Ala17 CTLA4 molecular variant (maximum logarithm of odds score (MLS) of 3.26) and allele 17 of the dinucleotide marker (MLS = 3.14) was observed in IBD-affected sibling pairs.
Conclusion
The CTLA4 gene is strongly associated with, and linked to IDDM in a Russian population.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset contains administrative polygons grouped by country (admin-0) with the following subdivisions according to Who's On First placetypes:
- macroregion (admin-1 including region)
- region (admin-2 including state, province, department, governorate)
- macrocounty (admin-3 including arrondissement)
- county (admin-4 including prefecture, sub-prefecture, regency, canton, commune)
- localadmin (admin-5 including municipality, local government area, unitary authority, commune, suburb)
The dataset also contains human settlement points and polygons for:
- localities (city, town, and village)
- neighbourhoods (borough, macrohood, neighbourhood, microhood)
The dataset covers activities carried out by Who's On First (WOF) since 2015. Global administrative boundaries and human settlements are aggregated and standardized from hundreds of sources and available with an open CC-BY license. Who's On First data is updated on an as-need basis for individual places with annual sprints focused on improving specific countries or placetypes. Please refer to the README.md file for complete data source metadata. Refer to our blog post for explanation of field names.
Data corrections can be proposed using Write Field, an web app for making quick data edits. You’ll need a Github.com account to login and propose edits, which are then reviewed by the Who's On First community using the Github pull request process. Approved changes are available for download within 24-hours. Please contact WOF admin about bulk edits.
Facebook
TwitterApache License, v2.0https://www.apache.org/licenses/LICENSE-2.0
License information was derived automatically
Biggest-Ru-Book Annotated by Balalaika
[!IMPORTANT] Official dataset for our INTERSPEECH 2026 paper "A Data-Centric Framework for Addressing Phonetic and Prosodic Challenges in Russian Speech Generative Models" (arXiv:2507.13563). Part of the Balalaika Russian speech data-processing pipeline — code: https://github.com/lab260ru/balalaika. If you use this resource, please cite it.
A curated Russian speech dataset for advanced speech generative tasks.
Overview… See the full description on the dataset page: https://huggingface.co/datasets/lab260/biggest_ru_book_balalaika.
Facebook
TwitterThis dataset is designed for research on audio deepfake detection, focusing specifically on generated speech in Russian. It contains TTS-generated audio, paired with transcriptions, and a mixed set for real vs fake classification tasks.
The main goal is to support research on audio deepfake detection in underrepresented languages, especially Russian. The dataset simulates real-world scenarios using multiple state-of-the-art TTS systems to generate fakes and includes clean, real audio data.
We used three high-quality TTS models to synthesize Russian speech:
XTTS-v2: Cross-lingual, zero-shot voice cloning with multilingual support.
Silero TTS: Lightweight, real-time Russian TTS model.
VITS RU Multispeaker: VITS-based Russian model with speaker variability.
For real human speech, we used a part of SOVA dataset, which contains clean Russian utterances recorded by multiple speakers.