Skip to main content
Big Cheese Studio S.A. logo

Big Cheese Studio S.A. — Investor Relations & Filings

Ticker · BCS ISIN · PLA340200015 LEI · 259400MSY0KV1BIRK132 WAR Publishing, broadcasting, and content production and distribution activities
Open in API
Filings indexed 600 across all filing types
Latest filing 2024-04-26 Audit Report / Informat…
Country PL Poland
Listing WAR BCS

About Big Cheese Studio S.A.

https://bigcheesestudio.com/index.php/e…

Big Cheese Studio S.A. is a video game developer specializing in the production and publication of realistic simulation games. The company is best known for its successful 'Cooking Simulator' franchise, which encompasses the original title, numerous downloadable content (DLC) packs, a virtual reality (VR) version, and a forthcoming sequel. The studio's portfolio also includes other simulation titles. Big Cheese Studio's games are characterized by their complexity, immersive gameplay, and high attention to detail, targeting players who seek realistic and engaging experiences.

Recent filings

Filing Released Lang Actions
Sprawozdanie Zarządu z działalności Spółki za 2023 - podpis
Audit Report / Information Classification · 95% confidence The document text provided is heavily truncated and appears to be the raw HTML/CSS structure generated by a PDF conversion tool (pdf2htmlEX), indicated by tags like 'html', 'head', 'style', and font definitions ('font-woff'). The title tag contains 'BCS_JSF_2023_SzDZ_2023-12-31_pl.xhtml', suggesting a document related to a specific date (2023-12-31) and possibly a Polish entity ('pl'). Crucially, the document length is very large (1,816,511 chars), suggesting it is the full content of a substantial report, not just a short announcement. Given the context of financial reporting and the large size, this is likely a comprehensive financial statement or report. However, without clear headers like '10-K', 'Annual Report', or 'Interim Report', and considering the file extension/name structure often associated with regulatory filings that are not standard SEC forms (like XBRL filings or local regulatory submissions), the most appropriate classification among the provided options for a large, comprehensive, non-standard report is either 'AR' (Audit Report / Information) or 'IR' (Interim / Quarterly Report), or potentially 'RNS' if it's a general regulatory filing. Since the content is not visible beyond the boilerplate HTML structure, and the file name suggests a year-end or period-end document ('2023-12-31'), it is most likely a full financial report. If it were a short announcement about a report, it would be RPA/RNS (Rule 2). Since it is a large file, it is the report itself. Without more context, 'IR' (Interim/Quarterly Report) is a reasonable guess for a large period-end document, but 'AR' (Audit Report/Information) is also plausible for a comprehensive filing. Given the structure often seen in non-US filings converted to HTML, and the lack of explicit '10-K' keywords, I will lean towards the general comprehensive report category that isn't the Annual Report, which is 'IR' (Interim / Quarterly Report), or 'AR' if it's an audit-focused document. Since the document is massive, it is the report content itself. Revisiting the definitions: '10-K' is for official yearly reports. 'IR' is for comprehensive reports shorter than a year. 'AR' is for standalone audit reports. Since the date is year-end (2023-12-31), it is most likely the Annual Report (10-K) or a related comprehensive filing. However, since '10-K' is specifically defined as the 'Official yearly report', and this document is clearly a large, converted file, I will classify it as '10-K' based on the year-end date, assuming it contains the full annual performance data, despite the lack of explicit '10-K' text in the snippet. FY 2023
2024-04-26 Polish
Sprawozdanie finansowe za 2023 - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML structure, specifically a digital signature block (XML Signature/XAdES) containing elements like <Signature>, <SignedInfo>, <SignatureValue>, <KeyInfo>, and <QualifyingProperties>. The content within the object tag references a file named "BCS_JSF_31-12-2023_2023-12-31_pl.xhtml" and includes CSS styling related to PDF rendering (like #page-container, .pf, .pc). This strongly suggests the document is a digitally signed container or wrapper for a financial report, likely an Annual Report (10-K) or an Interim Report (IR), given the date range (31-12-2023). However, the document itself is not the report content but the signature metadata. Since the content is a digital signature wrapper and the underlying document appears to be a comprehensive report (implied by the CSS/HTML structure for a full document), and given the lack of explicit '10-K' or 'IR' headers in the visible text, the most appropriate classification for a document that is primarily a regulatory/official signature wrapper, especially one that doesn't fit neatly into the announcement categories (RPA/RNS), is the general Regulatory Filings category (RNS). If the underlying document were clearly identifiable as a 10-K or IR, that would be preferred, but here we only see the signature structure and hints of an underlying document structure.
2024-04-26 Polish
Sprawozdanie finansowe za 2023 - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists entirely of XML structures related to digital signatures, specifically containing elements like 'Signatures', 'SignedInfo', 'SignatureValue', 'X509Data', and 'SigningTime'. This structure is characteristic of an XML Digital Signature (XML-DSig) block, often used to validate the authenticity and integrity of an associated document (which is referenced via the 'Reference' URI pointing to 'BCS_JSF_31-12-2023_2023-12-31_pl.xhtml'). Since the text itself is not the report content but rather the cryptographic proof of signing for a document dated 31-12-2023, and it does not contain any narrative, financial highlights, or management discussion, it does not fit standard reporting categories like 10-K, ER, or IR. It is a technical component of a filing. Given the options, this highly technical, non-narrative component is best categorized as a general 'Regulatory Filing' (RNS) or potentially a technical attachment, but RNS serves as the best general fallback for non-standard, technical regulatory components that aren't explicitly defined elsewhere.
2024-04-26 Polish
Sprawozdanie finansowe za 2023 - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML digital signature blocks (Signature, SignedInfo, Reference, DigestValue, KeyInfo, X509Data, etc.). This structure is characteristic of a digitally signed file, often used to verify the authenticity and integrity of an underlying document. The reference URI points to a file named "BCS_JSF_31-12-2023_2023-12-31_pl.xhtml", and the signing time is April 26, 2024. The content itself is not the financial report but the cryptographic wrapper around it. Since the document is extremely short (5509 chars) and appears to be an announcement or wrapper rather than the full report, and given the presence of a specific file reference, this strongly suggests a Report Publication Announcement (RPA) or a general Regulatory Filing (RNS) announcing the availability of the signed document. Given the context of financial reporting, an RPA is more specific if this signature block is attached to a brief notice stating the report is available. However, without the actual announcement text, and seeing only the signature structure, the safest classification that covers metadata/wrapper documents is RNS, unless the structure strongly implies a specific type of announcement. The presence of the file name 'BCS_JSF_31-12-2023' suggests a document related to year-end results (31-12-2023). Since this is just the signature block and not the report content, and it doesn't fit ER, IR, or 10-K, RNS is the most appropriate fallback for a regulatory artifact that isn't a primary report type.
2024-04-26 Polish
Sprawozdanie finansowe za 2023
Audit Report / Information Classification · 95% confidence The document text provided is an HTML representation of a document converted from a PDF, indicated by the presence of extensive CSS styling related to page layout (e.g., '.pf', '.pc', '.t') and the title tag containing 'BCS_JSF_31-12-2023_2023-12-31_pl.xhtml'. The content itself is heavily technical, containing font definitions and structural elements typical of a converted financial filing. The filename suggests a report ending on December 31, 2023. Given the structure and the fact that it is a complete document (not just an announcement of one), and it covers a full year (implied by the 31-12-2023 date), it is most likely an Annual Report (10-K) or a comprehensive year-end report. Since '10-K' is the standard US SEC designation for an Annual Report, and this appears to be a full, detailed filing (indicated by the massive character count of 2.4 million characters), 10-K is the most appropriate classification for a comprehensive annual filing, even if the source jurisdiction is Polish (implied by 'pl' in the filename). FY 2023
2024-04-26 Polish
List do Akcjonariuszy - podpis
Regulatory Filings Classification · 95% confidence The provided document text consists almost entirely of XML digital signature blocks (Signatures, SignedInfo, SignatureValue, KeyInfo, X509Certificate, etc.). This structure is characteristic of a digitally signed document, often used to verify the authenticity and integrity of an official filing or attachment. The reference URI within the signature block points to 'BCH_list_do_akcjonariuszy_31-12-2023.xhtml', which translates roughly to 'List of shareholders as of 31-12-2023'. A list of shareholders is a specific type of regulatory or governance disclosure. Since the document itself is just the signature wrapper and not the content of the shareholder list or a formal report like a 10-K or IR, and given the specific nature of the content referenced (shareholder list), it is most likely an attachment or component of a larger filing. However, without the actual content, and given the highly technical, non-narrative nature of the text, it does not fit standard report types (10-K, IR, ER). It is a technical component of a filing. The closest fit among the provided options for specific regulatory/governance components that might be attached or referenced this way, especially involving shareholder data, is difficult to pinpoint exactly. However, since it is a technical artifact (a signature block) and not the primary report, and it relates to shareholder data, it is best classified as a general Regulatory Filing (RNS) or potentially related to Governance (CGR) or Voting (DVA). Given the structure is purely technical metadata for verification, RNS (Regulatory Filings - fallback for miscellaneous/technical filings) is the safest classification, as it is not the report itself, nor is it a standard announcement (like RPA). The document length is moderate (5333 chars), but the content is purely signature data, not a narrative announcement.
2024-04-26 Polish

Browse filings by year

8 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.