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,569 across all filing types
Latest filing 2025-03-25 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
zal04_Sprawozdanie_Zarzadu_z_dzialalnosci_Grupy_CD_PROJEKT_za_2024_r.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is heavily truncated and appears to be the raw HTML/XML structure generated from converting a PDF document, indicated by tags like 'html', 'head', 'style', and font definitions ('@font-face'). Crucially, the document length is extremely large (15,857,221 chars), suggesting it is a full, comprehensive report, not a short announcement. However, the provided text snippet itself does not contain any recognizable financial headers, regulatory language (like '10-K', '10-Q', 'Proxy Statement'), or specific content that definitively points to one of the detailed categories (like ER, IR, AR, DEF 14A). Given the massive size, it is highly likely to be a full report (10-K or IR). Since the content is unreadable due to truncation and formatting noise, and there is no explicit mention of 'Annual Report' or 'Quarterly Report', I must rely on the context of typical large filings. The presence of extensive font data and HTML structure suggests a complex, multi-page document. Without content keywords, classifying it as the specific report type (10-K or IR) is impossible. The safest classification for a large, unidentifiable regulatory document that isn't clearly an announcement is the general fallback category for regulatory filings that don't fit elsewhere, or to assume the largest possible report type if the size implies it. Revisiting the definitions: 10-K is the 'Official yearly report'. IR is the 'Comprehensive financial report for a period shorter than a year'. Since the document is massive, it is one of these two. Given the ambiguity, and the fact that the text is just the container structure, I will default to the most comprehensive annual filing, 10-K, but acknowledge the low confidence due to the lack of actual content. *Self-Correction based on Rules:* Rule 2 (MENU VS MEAL) applies to short documents announcing a report. This document is massive, suggesting it *is* the report content, even if the content is garbled HTML. Therefore, I should try to classify it as the report itself. Since I cannot read the content to distinguish between Annual (10-K) and Interim (IR), and 10-K is the primary annual filing, I will select 10-K as the best guess for a very large, comprehensive filing, while assigning a moderate confidence score due to the unreadable nature of the provided snippet. Q3 2024
2025-03-25 Polish
zal08_Jednostkowe_sprawozdanie_finansowe_CD_PROJEKT_za_2024.xhtml.xades
Regulatory Filings Classification · 1% confidence The document text consists of XML digital signature blocks (XAdES format) referencing an external file named 'Jednostkowe sprawozdanie finansowe CD PROJEKT za 2024.xhtml'. This indicates the document is a digital signature wrapper or a certification file for a financial report, rather than the financial report itself. According to the Certification Rule, documents that are primarily officer certifications or attestations should be classified as Regulatory Filings (RNS). FY 2024
2025-03-25 Polish
zal12_Jednostkowe_sprawozdanie_finansowe_CD_PROJEKT_za_2024.xhtml
Audit Report / Information Classification · 1% confidence The provided document text is heavily truncated and appears to be the raw HTML/XML structure of a converted PDF file, indicated by tags like 'html', 'head', 'meta', 'style', and font definitions ('@font-face'). There is no discernible content related to financial results, management changes, or specific regulatory disclosures (like 10-K, ER, or DEF 14A). The document length is extremely large (over 11 million characters), suggesting it is a full report, but the visible text is only the structural boilerplate from the conversion process. Given the lack of substantive content and the nature of the text (which is often the result of converting a large filing like an Annual Report or Quarterly Report into a text format), and the fact that we cannot confirm the actual content, the safest classification based on the provided snippet is the general fallback category for regulatory filings that don't fit elsewhere, or if we assume this is the underlying structure of a major filing that was poorly extracted, we might lean towards a comprehensive report. However, since the text itself is purely structural boilerplate and does not contain any keywords identifying it as a 10-K, IR, or ER, and it is not an announcement of a report (RPA), the most appropriate classification for unidentifiable regulatory data is RNS (Regulatory Filings). Given the massive size, it is likely a full report, but without content, RNS is the fallback. Q3 2024
2025-03-25 Polish
zal07_2025.03.25._The_Supervisory_Board_declaration_regarding_the_Audit_Committee.xhtml
Audit Report / Information Classification · 1% confidence The document text provided is an HTML structure containing embedded CSS and font data, which is characteristic of a converted PDF file. The length is substantial (957,670 characters), suggesting it is a full report rather than a brief announcement. The content, although heavily obfuscated by the conversion artifacts, contains sequences of characters that strongly resemble financial data, tables, and potentially narrative sections typical of comprehensive corporate filings. Given the large size and the nature of the content (even if unreadable in detail), it is highly likely to be a full annual or interim report, rather than a short announcement (RPA/RNS). Since the text is too long and complex to be a simple 'Earnings Release' (ER) or a short 'Fund Factsheet' (FS), and without explicit headers like '10-K' or 'Annual Report', the most appropriate classification for a comprehensive, long-form financial document that isn't explicitly an Annual Report (10-K) or an Interim Report (IR) based on explicit period markers is to look for the most comprehensive category. However, the presence of complex, repeating sequences and the sheer volume strongly suggest a primary financial filing. Since the text is too long to be an RPA/RNS, and it appears to be the full content, I will lean towards the most comprehensive financial report types. Given the lack of explicit '10-K' or 'IR' headers in the visible text, and the structure suggesting a full document dump, I will re-evaluate based on the provided definitions. The structure is too complex for a simple ER or FS. If this were a full annual filing, it would be a 10-K or IR. Since the text is a raw dump of a converted document, and it is very long, it represents the full content of a report. Without explicit period markers, classifying it as a general 'Interim / Quarterly Report' (IR) or 'Annual Report' (10-K) is a strong possibility. Given the ambiguity, and the fact that this is a massive data dump, I will check for keywords related to comprehensive reports. The presence of complex, repeating character sequences that look like encoded data or heavily formatted text often occurs when converting large financial statements. I will default to the most comprehensive report type that isn't explicitly the 10-K, which is the Interim Report (IR), or if the size implies annual, 10-K. Since the document is extremely large (nearly 1MB), it is most likely the Annual Report (10-K) or a very detailed Interim Report (IR). Given the high confidence required, and the lack of explicit headers, I will use the 'Interim / Quarterly Report' (IR) as a strong candidate for a comprehensive report that isn't the 10-K, or the '10-K' itself. Given the massive size, 10-K is statistically more likely for a full document dump unless it's a half-year report. I will select 10-K as the default for a massive, full financial document dump. Q3 2024
2025-03-25 Polish
zal04_2025.03.25_The_Supervisory_Board_assessment_of_financial_statements.xhtml
Environmental & Social Information Classification · 1% confidence The document text provided is an HTML structure containing embedded CSS and font data, which is characteristic of a converted PDF file. The document length is very large (2,616,560 characters), suggesting it is a comprehensive report rather than a brief announcement. The content, although heavily truncated and encoded in the provided snippet, shows complex financial and structural data typical of a full regulatory filing or annual report. Given the size and the nature of the content (which often includes detailed financial statements, management discussion, and extensive notes when fully rendered), and lacking specific headers like '10-K' or 'Annual Report', the most appropriate classification for a large, comprehensive, non-specific filing that is not clearly an earnings release (ER) or interim report (IR) is often the Annual Report (10-K) if it covers a full year, or a general comprehensive report. However, since the text itself is not readable for specific section titles (like 'Consolidated Financial Statements' or 'Item 7. Management's Discussion and Analysis'), and it is clearly a full document conversion, I must rely on the size and the general context of financial reporting. Since the document is extremely large, it strongly suggests a full annual filing (10-K) or a comprehensive quarterly filing (IR). Without explicit confirmation of 'Annual' or 'Quarterly', and given the high volume of data, I will lean towards the most comprehensive yearly report type, 10-K, as a strong possibility for such a large file, or use the general 'Regulatory Filings' (RNS) if the content is too ambiguous. Upon closer inspection of the encoded text, the presence of complex data structures and the sheer size strongly suggest a primary financial filing. Since 10-K is the primary annual filing, and the size is indicative of a full report, I will classify it as 10-K, assuming it is the annual filing, as it is the largest category available besides the general RNS.
2025-03-25 Polish
zal03_CD_PROJEKT_2024_atestacja_ESG_skonsolidowane_PL.xhtml.XAdES
Environmental & Social Information Classification · 1% confidence The provided document text consists entirely of XML Digital Signature elements, specifically containing 'Signatures', 'SignedInfo', 'SignatureValue', 'KeyInfo', and 'QualifyingProperties'. This structure is characteristic of a digitally signed document, often used to certify the authenticity and integrity of an attached file or report. The reference URI points to 'CD_PROJEKT_2024_atestacja_ESG_skonsolidowane_PL.xhtml', suggesting the signed content is an ESG report or related document. Since the text itself is only the signature block and not the content of the ESG report, and it is a formal certification, it is best classified as a general Regulatory Filing (RNS) or potentially related to ESG (SR). Given the highly technical nature of the content (XML signature) and the lack of narrative content describing ESG performance, RNS is the most appropriate general classification for a technical certification artifact that doesn't fit a specific report type, although the underlying document is ESG-related. However, since the content strongly implies a formal certification of a document, and the document length is relatively short (5358 chars), it is likely an announcement or attachment wrapper. Given the options, and the presence of 'atestacja_ESG' (ESG certification) in the URI, if the underlying document were present, it would be SR. As this is just the signature block, RNS is the safest fallback for a non-standard filing artifact, but I will lean towards SR as the signature is explicitly tied to an ESG document.
2025-03-25 Polish

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.