biztrac. BETA
COMPANY REGISTER PROFILE
984990804 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠BR RAAKEN AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Site preparation

BR RAAKEN AS

Org. no. 984990804 Limited company (AS) Trondheim Incorporated 2002 In liquidation
Revenue 2025 NOK 1.8m
Operating profit NOK −238,000
Equity NOK 322,000
Incorporated 2002
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

BR RAAKEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984990804. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre oppdrag innenfor grunnarbeide som graving og annen maskinkjøring samt tilhørende mur/puss og betongarbeider. Investering i fast eiendom for utleie og dertil knyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −238,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▼ −60 %
Operating profit
NOK −238,000
▼ −158 %
Equity
NOK 322,000
▼ −50 %

Financial health · 2025

Liquidity
2.04
Very good
Current assets ÷ current liabilities
Profitability
-8.2%
Not satisfactory
Return on total assets
Solidity
15.2%
Satisfactory
Equity as a share of total capital

Who owns BR RAAKEN AS?

BR RAAKEN AS
NOK 1.8m rev. · NOK −238,000 profit

BR RAAKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BR RAAKEN AS

Who owns BR RAAKEN AS?

Marcus Steen Raaken is the largest registered owner, with 50.0%.

What is the revenue of BR RAAKEN AS?

BR RAAKEN AS had revenue of NOK 1.8m in 2025.

Where is BR RAAKEN AS based?

BR RAAKEN AS has its business address in Trondheim.

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.