BIZTRAC BETA
Development of building projects

BEKKELØKKA BOLIG AS

Org. no. 933326977 Limited company (AS) Færder Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK −295,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

BEKKELØKKA BOLIG AS is registered as a limited company in Færder, Vestfold with organisation number 933326977. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom, rådgivning og deltakelse i andre virksomheter, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK −295,000

Financial health · 2025

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

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

Who owns BEKKELØKKA BOLIG AS?

ØSTBORG BERNTSEN HOLDING AS
BEKKELØKKA BOLIG AS
NOK 0 rev. · NOK −17,000 profit

BEKKELØKKA BOLIG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEKKELØKKA BOLIG AS

Who owns BEKKELØKKA BOLIG AS?

ØSTBORG BERNTSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of BEKKELØKKA BOLIG AS?

BEKKELØKKA BOLIG AS had revenue of NOK 0 in 2025.

Where is BEKKELØKKA BOLIG AS based?

BEKKELØKKA BOLIG AS has its business address in Nøtterøy.

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.