BIZTRAC BETA
Uoppgitt

F2 EIENDOM AS

Org. no. 919300892 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −31,000
Equity NOK −2.2m
Incorporated 2017
Share capital NOK 3.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

F2 EIENDOM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 919300892. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 3.0m, divided into 3030 shares. The company's stated purpose is: “Investere i og eie andeler og aksjer i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK −2.2m

Financial health · 2025

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

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

Who owns F2 EIENDOM AS?

BØK EIENDOM AS
F2 EIENDOM AS
NOK 0 rev. · NOK −31,000 profit

F2 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does F2 EIENDOM AS own?

F2 EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about F2 EIENDOM AS

Who owns F2 EIENDOM AS?

BØK EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of F2 EIENDOM AS?

F2 EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of F2 EIENDOM AS?

Kenneth Fredriksen is registered as general manager of F2 EIENDOM AS.

Where is F2 EIENDOM AS based?

F2 EIENDOM AS has its business address in Sandefjord.

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.