BIZTRAC BETA
Rental and operating of own or leased real estate

FIKKJEBAKKE LAGER AS

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

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-12.

FIKKJEBAKKE LAGER AS is registered as a limited company in Kragerø, Telemark with organisation number 936547478. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Å eie, utvikle og drive minilager- og lagerhotellvirksomhet, herunder kjøp, salg, utvikling og utleie av fast eiendom, samt virksomhet som står i naturlig forbindelse med dette. Selskapet kan videre eie, drive og delta i andre selskaper og virksomheter.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 18,000
Est. value
NOK 17,000

Financial health · 2025

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

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

Who owns FIKKJEBAKKE LAGER AS?

V-XL-55 AS
FIKKJEBAKKE LAGER AS
· NOK −15,000 profit

FIKKJEBAKKE LAGER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FIKKJEBAKKE LAGER AS

Who owns FIKKJEBAKKE LAGER AS?

V-XL-55 AS is the largest registered owner, with 75.0%.

Who is the general manager of FIKKJEBAKKE LAGER AS?

Morten Møklegård is registered as general manager of FIKKJEBAKKE LAGER AS.

Where is FIKKJEBAKKE LAGER AS based?

FIKKJEBAKKE LAGER 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.