Skip to main content
CD Projekt logo

CD Projekt — Investor Relations & Filings

Ticker · CDR ISIN · PLOPTTC00011 LEI · 259400TYO5Q8SH8TL437 WAR Publishing, broadcasting, and content production and distribution activities
Open in API
Filings indexed 1,595 across all filing types
Latest filing 2024-03-28 Audit Report / Informat…
Country PL Poland
Listing WAR CDR

About CD Projekt

https://www.cdprojekt.com/en/

CD Projekt is a video game company that operates through two primary segments: its development studio, CD PROJEKT RED, and its digital distribution platform, GOG.com. The company is renowned for developing critically acclaimed, story-driven role-playing games (RPGs) that emphasize narrative depth and technical innovation. Its flagship franchises include the globally recognized "The Witcher" series and the futuristic open-world game "Cyberpunk 2077". CD PROJEKT RED focuses on creating immersive worlds with memorable stories and high production quality, targeting a global audience of gamers who appreciate expansive gameplay and complex narratives.

Recent filings

Filing Released Lang Actions
zal02_Supervisory_Board_Statement_-_Audit_Committee.xhtml
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing CSS styling and font definitions, which strongly suggests it is the raw output of a PDF-to-HTML conversion process (indicated by the generator meta tag 'pdf2htmlEX' and the extensive CSS for layout). The actual content is heavily truncated and appears to be the beginning of a document, but the structure itself does not contain typical keywords for any specific financial filing type (like '10-K', 'Earnings Release', 'Proxy Statement', etc.). Given the nature of the input (a large, complex, but seemingly incomplete or structurally focused document dump) and the lack of substantive financial or regulatory text, the most appropriate classification based on the provided definitions is the fallback category for miscellaneous or unclassifiable regulatory filings, or potentially a document that announces a report but is itself just the wrapper. Since the document length is very large (2.4M chars), it is unlikely to be a simple RPA/RNS announcement wrapper, but without content, classification is impossible. I will default to the general regulatory filing fallback (RNS) as the safest option when content is inaccessible or non-specific, while noting the low confidence due to the structural nature of the provided text snippet. Q3 2024
2024-03-28 Polish
zal01_Supervisory_Board_Assesment_-_Consolidated_Statement.xhtml
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing embedded CSS and font data, which is characteristic of a rendered PDF or a document viewer interface, rather than the content of a standard financial filing itself. The document length is very large (2,522,193 characters), suggesting it is a full report or a large collection of data. However, the actual visible content is just the boilerplate structure of the HTML rendering engine (pdf2htmlEX). Since the actual financial content is not visible, and the structure suggests a large document that has been processed for viewing, I must rely on the context that this is a 'financial document classifier'. Given the lack of specific keywords (like '10-K', 'Earnings Release', 'Proxy Statement', etc.) in the visible text, and the fact that the text is just the container structure, this is highly ambiguous. In such cases where the content is inaccessible or appears to be metadata/rendering artifacts, the safest classification is the general fallback category for regulatory filings that don't fit elsewhere, or to assume it is a large report that failed to render its content properly. Given the massive size, it is unlikely to be a short announcement (RPA/RNS). I will default to the most comprehensive report type, the Annual Report (10-K), as a high-confidence guess for a very large document, but acknowledge the severe lack of evidence. Re-evaluating based on the 'MENU VS MEAL' rule: If the text is just the container, it's not the meal. However, the document length is huge, suggesting the 'meal' is present but truncated/unreadable. Since I cannot confirm the content, I will use the most general regulatory filing code (RNS) as the fallback for unclassifiable content, as the structure itself is not a specific report type. Q3 2024
2024-03-28 Polish
zal04_Managment_Board_report.xhtml
Management Reports Classification · 95% confidence The document text provided is an HTML structure containing embedded CSS and font definitions, which is characteristic of a document that has been converted from a native format (like PDF) into HTML for web viewing or processing. The actual content is heavily truncated, but the structure strongly suggests this is not the primary filing document itself (like a 10-K or IR). Given the massive file size (13,771,360 characters) and the fact that the provided text is just the header/metadata/styling of the converted file, this is likely a wrapper or a placeholder for a larger document. However, without substantive content, I must rely on the context of typical filings. Since the text is clearly a conversion artifact and not the report narrative, and there is no explicit announcement text (like 'Report Attached'), I will look for clues in the structure. The structure itself doesn't point to a specific filing type (like ER or 10-K). In the absence of content, and considering this is a database classification task, if the underlying document was a standard report, this HTML wrapper is often associated with the report itself. Given the extreme length, it is highly unlikely to be a short announcement (RPA/RNS). I will assume, based on the sheer volume of data implied by the length, that this is a comprehensive report, and since no specific quarterly/half-yearly indicators are present, the default comprehensive annual report (10-K) is a strong candidate, or perhaps an Investor Presentation (IP) or Interim Report (IR) if it were quarterly. Since I cannot confirm the period, and the text is just the conversion shell, I will default to the most comprehensive report type that could generate such a large file, which is the Annual Report (10-K), while acknowledging the low confidence due to missing content. Re-evaluating the definitions: The document length is massive (13.7 million chars), suggesting a full, detailed report, not a brief announcement. The structure is a conversion artifact. I will classify it as the most comprehensive report, 10-K, as it is the largest standard filing.
2024-03-28 Polish
zal05_Consolidated_financial_statement_of_the_CD_PROJEKT_GROUP_for_2023.xhtml
Audit Report / Information Classification · 95% confidence The document text provided is an HTML structure containing embedded CSS and font data, which is characteristic of a converted PDF file. The actual content is heavily truncated (only the first 15000 characters are shown, but the total length is over 15 million characters), and the visible text is primarily metadata, font definitions, and structural elements, not substantive financial reporting content. Given the massive size (15M characters), it suggests a very large, comprehensive document. However, without any discernible keywords related to specific SEC forms (like 10-K, DEF 14A) or specific report types (like Earnings Release, Audit Report), and considering the format is a raw HTML conversion of a document, the most appropriate classification based on the provided definitions and the 'MENU VS MEAL' rule is to look for a general category. Since the document is clearly a large, complex report that has been processed, and we cannot confirm its specific nature (10-K vs IR vs AR), the fallback category 'Regulatory Filings' (RNS) is used for miscellaneous or unclassifiable filings, or if the document is merely an announcement of a report. Given the sheer size, it is likely a full report, but the lack of content prevents specific classification. I will lean towards the most comprehensive report type that fits a large filing, which is often the Annual Report (10-K), but since the text is unreadable and looks like a conversion artifact, I will use the fallback 'RNS' as it covers miscellaneous filings that don't fit elsewhere, or if this is an attachment wrapper. Given the ambiguity and lack of content, RNS is the safest fallback for an unidentifiable large document. Q3 2024
2024-03-28 Polish
zal05_Oswiadczenie_Rady_Nadzorczej_-_w_sprawie_Komitetu_Audytu_.xhtml
Audit Report / Information Classification · 95% confidence The document text provided is extremely short (relative to the expected length of a full report like a 10-K or IR) and appears to be the raw HTML/XML structure generated from converting a PDF document using a tool like pdf2htmlEX. Crucially, the text itself does not contain any financial statements, management discussion, or specific regulatory headers (like '10-K' or 'Interim Report'). Instead, it contains styling information, font definitions, and structural tags typical of a document conversion artifact. Given the nature of the input—a truncated, structural representation of a document rather than the content itself—and the rule stating that short documents announcing a report's availability should be classified as RPA or RNS, this input most likely represents an announcement or a placeholder for a filing rather than the filing content itself. Since there is no explicit announcement text (like 'Report attached'), the safest classification for an unidentifiable, structural document snippet that is not a full report is the general fallback category. Q3 2024
2024-03-28 Polish
zal02_Oswiadczenie_Rady_Nadzorczej_-_sprawozdanie_skonsolidowane.xhtml
Audit Report / Information Classification · 95% confidence The provided document text is heavily truncated and appears to be the raw HTML/XML structure generated from converting a PDF document, indicated by tags like '<html xmlns="http://www.w3.org/1999/xhtml">', '<meta name="generator" content="pdf2htmlEX">', and extensive CSS styling. The document length is very large (2,464,139 chars), suggesting it is a full report, but the content provided is only the structural boilerplate and not the substantive financial text. According to Rule 2 (The 'MENU VS MEAL' Rule), if a document is short and announces a report, it should be classified as RPA or RNS. However, the metadata indicates the *True Document Length* is very large, suggesting the full document is substantial, even if the provided snippet is just the wrapper. Since the actual content (financial tables, narrative, footnotes) is missing, and we only see the conversion artifacts, we cannot definitively classify it as 10-K, IR, or ER. The most appropriate classification for a document that is clearly a regulatory filing wrapper but whose content type is obscured by the conversion artifact is the general fallback category, Regulatory Filings (RNS), as it is a filing that doesn't fit a specific content type based on the visible text. Q3 2024
2024-03-28 Polish

Browse filings by year

11 years

Report missing filing

Can't find a specific document? Let us know and we'll add it within 24 hours.

We will notify you once the filing is added.
Report sent
Thank you. We will check the data and update it shortly.