BIZTRAC BETA
Joinery installation

BESTER BYGG AS

Org. no. 831875712 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 114,000
Operating profit NOK −172,000
Equity NOK −228,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

BESTER BYGG AS is registered as a limited company in Bærum, Akershus with organisation number 831875712. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg og anlegg, kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 114,000 in revenue and NOK −172,000 in operating profit.

Key figures · 2025

Revenue
NOK 114,000
Operating profit
NOK −172,000
Equity
NOK −228,000

Financial health · 2025

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

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

Who owns BESTER BYGG AS?

MARIA EGGEN HEDENSTAD
BESTER BYGG AS
NOK 114,000 rev. · NOK −172,000 profit

BESTER BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BESTER BYGG AS

Who owns BESTER BYGG AS?

MARIA EGGEN HEDENSTAD is the largest registered owner, with 50.0%.

What is the revenue of BESTER BYGG AS?

BESTER BYGG AS had revenue of NOK 114,000 in 2025.

Who is the general manager of BESTER BYGG AS?

Jonathan Simon Bester is registered as general manager of BESTER BYGG AS.

Where is BESTER BYGG AS based?

BESTER BYGG AS has its business address in Lommedalen.

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.