BIZTRAC BETA
Development of building projects

FIKKJEBAKKEN EIENDOM AS

Org. no. 931219650 Limited company (AS) Kragerø Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK −15,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

FIKKJEBAKKEN EIENDOM AS is registered as a limited company in Kragerø, Telemark with organisation number 931219650. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, drift av fast eiendom og andre produkter og tjenester som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK −15,000

Financial health · 2025

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

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

Who owns FIKKJEBAKKEN EIENDOM AS?

EF EIENDOM AS
FIKKJEBAKKEN EIENDOM AS
NOK 0 rev. · NOK −18,000 profit

FIKKJEBAKKEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIKKJEBAKKEN EIENDOM AS

Who owns FIKKJEBAKKEN EIENDOM AS?

EF EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FIKKJEBAKKEN EIENDOM AS?

FIKKJEBAKKEN EIENDOM AS had revenue of NOK 0 in 2025.

Where is FIKKJEBAKKEN EIENDOM AS based?

FIKKJEBAKKEN EIENDOM AS has its business address in Helle.

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.