BIZTRAC BETA
Development of building projects

NØSTE HOVEDGÅRD AS

Org. no. 935743214 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 77,000
Operating profit NOK −219,000
Equity NOK 3.0m
Incorporated 2025
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−219k kr).

NØSTE HOVEDGÅRD AS is registered as a limited company in Drammen, Buskerud with organisation number 935743214. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2025. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av fast eiendom samt ved kjøp av aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 77,000 in revenue and NOK −219,000 in operating profit.

Key figures · 2025

Revenue
NOK 77,000
Operating profit
NOK −219,000
Equity
NOK 3.0m
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns NØSTE HOVEDGÅRD AS?

BRAKOHUS AS
NØSTE HOVEDGÅRD AS
NOK 77,000 rev. · NOK −219,000 profit

NØSTE HOVEDGÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NØSTE HOVEDGÅRD AS

Who owns NØSTE HOVEDGÅRD AS?

BRAKOHUS AS is the largest registered owner, with 100.0%.

What is the revenue of NØSTE HOVEDGÅRD AS?

NØSTE HOVEDGÅRD AS had revenue of NOK 77,000 in 2025.

Who is the general manager of NØSTE HOVEDGÅRD AS?

Bjørn-Aksel Hjelmtvedt is registered as general manager of NØSTE HOVEDGÅRD AS.

Where is NØSTE HOVEDGÅRD AS based?

NØSTE HOVEDGÅRD AS has its business address in Drammen.

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.