BIZTRAC BETA
Development of building projects

FLAKKSVANN BOLIG AS

Org. no. 999542603 Limited company (AS) Birkenes Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK −361,000
Incorporated 2012
Share capital NOK 100,000

Signals

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

FLAKKSVANN BOLIG AS is registered as a limited company in Birkenes, Agder with organisation number 999542603. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling, utbygging, utleie, kjøp og salg av fast eiendom og eiendomsprosjekter, herunder oppføring av nybygg, innredning, restaurering av bygg, snekkervirksomhet og utleie av arbeidskraft, samt alt hva hermed står i forbindelse, herunder deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −11,000
Equity
NOK −361,000

Financial health · 2025

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

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

Who owns FLAKKSVANN BOLIG AS?

GE BIRKELAND INVEST AS
FLAKKSVANN BOLIG AS
· NOK −11,000 profit

FLAKKSVANN BOLIG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FLAKKSVANN BOLIG AS

Who owns FLAKKSVANN BOLIG AS?

GE BIRKELAND INVEST AS is the largest registered owner, with 50.0%.

Who is the general manager of FLAKKSVANN BOLIG AS?

Olav Birkeland is registered as general manager of FLAKKSVANN BOLIG AS.

Where is FLAKKSVANN BOLIG AS based?

FLAKKSVANN BOLIG AS has its business address in Birkeland.

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.