BIZTRAC BETA
Uoppgitt

RAKAFANT AS

Org. no. 999642373 Limited company (AS) Lier Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14
Equity NOK 54,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14 kr).
  • Nylig endring 2026-02-04 Adresseendring registrert 2026-02-04.

RAKAFANT AS is registered as a limited company in Lier, Buskerud with organisation number 999642373. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Holdingselskap, kjøp og salg av aksjer og andre finansielle aktiva.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14
Equity
NOK 54,000
Est. value
NOK 355,000

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RAKAFANT AS?

JENS-KRISTIAN HAUG
RAKAFANT AS
NOK 0 rev. · NOK −14 profit

RAKAFANT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAKAFANT AS own?

RAKAFANT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAKAFANT AS

Who owns RAKAFANT AS?

JENS-KRISTIAN HAUG is the largest registered owner, with 100.0%.

What is the revenue of RAKAFANT AS?

RAKAFANT AS had revenue of NOK 0 in 2025.

Who is the general manager of RAKAFANT AS?

Stian Tollefsen is registered as general manager of RAKAFANT AS.

Where is RAKAFANT AS based?

RAKAFANT AS has its business address in Lierskogen.

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.