BIZTRAC BETA
COMPANY REGISTER PROFILE
986942823 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

HYTTEBYGGEREN AS

Org. no. 986942823 Limited company (AS) Bergen Incorporated 2004 Active
Ownership graph ↗
Equity NOK −30,000
Incorporated 2004
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−30k kr).

HYTTEBYGGEREN AS is registered as a limited company in Bergen, Vestland with organisation number 986942823. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utvikling og salg av eiendom samt dertilhørende virksomhet.”.

Key figures · 2025

Equity
NOK −30,000

Financial health · 2025

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

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

Who owns HYTTEBYGGEREN AS?

HYTTEBYGGEREN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HYTTEBYGGEREN AS

Who owns HYTTEBYGGEREN AS?

KTD AS is the largest registered owner, with 50.0%.

Where is HYTTEBYGGEREN AS based?

HYTTEBYGGEREN AS has its business address in Fyllingsdalen.

Property

Business address Bjørgelien 19, 5141 Fyllingsdalen
Cadastral unit 4601-29/563/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 10 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.