BIZTRAC BETA
Business and other management consultancy activities

RACCE AS

Org. no. 847413662 Limited company (AS) Trondheim Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −32,000
Equity NOK 141.2m
Incorporated 1988
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−32k kr).

RACCE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 847413662. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1988. Registered share capital is NOK 100,000. The company's stated purpose is: “Drive industri-, handelsvirksomhet og skipsfart på inn- og utland og alt som derved står i forbindelse, samt ved aksjetegning eller på annen måte å delta i slik eller annen virksomhet alene eller i samarbeide med andre foretagender og interesser.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK 141.2m
Est. value
NOK 619.9m

Financial health · 2024

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

Who owns RACCE AS?

BJØRN CHRISTIAN EIDE
RACCE AS
NOK 0 rev. · NOK −32,000 profit

RACCE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RACCE AS own?

RACCE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RACCE AS

Who owns RACCE AS?

BJØRN CHRISTIAN EIDE is the largest registered owner, with 50.0%.

What is the revenue of RACCE AS?

RACCE AS had revenue of NOK 0 in 2024.

Where is RACCE AS based?

RACCE 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 15.06.2026.

Report a problem

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