biztrac. BETA
COMPANY REGISTER PROFILE
926821393 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Research and experimental development on social sciences and humanities

DEBATTENE OM NORGES FREMTID AS

Org. no. 926821393 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −120,000
Equity NOK 541,000
Incorporated 2021
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−120k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DEBATTENE OM NORGES FREMTID AS is registered as a limited company in Oslo, Oslo with organisation number 926821393. The business is classified under research and experimental development on social sciences and humanities (NACE 72.200). The company was incorporated in 2021. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Analysere, belyse og drøfte vesentlige temaer i en tid med gjennomgripende samfunnsendringer.”.

Former names: FC HOLDING XI AS

Key figures · 2025

Operating profit
NOK −120,000
▲ +85 %
Equity
NOK 541,000
▼ −14 %
Est. value
NOK 880,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns DEBATTENE OM NORGES FREMTID AS?

DEBATTENE OM NORGES FREMTID AS
· NOK −120,000 profit

DEBATTENE OM NORGES FREMTID AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEBATTENE OM NORGES FREMTID AS

Who owns DEBATTENE OM NORGES FREMTID AS?

FERD AS is the largest registered owner, with 100.0%.

Where is DEBATTENE OM NORGES FREMTID AS based?

DEBATTENE OM NORGES FREMTID AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.