BIZTRAC BETA
Development of building projects

NBH UTVIKLING AS

Org. no. 998461073 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 1.9m
Equity NOK 9.4m
Incorporated 2012
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NBH UTVIKLING AS is registered as a limited company in Øygarden, Vestland with organisation number 998461073. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Boligproduksjon, kjøp og salg av eiendom, prosjektutvikling herunder salg av tomter og bygninger samt å interessere seg i andre foretak og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK 1.9m
Equity
NOK 9.4m
Est. value
NOK 10.8m

Financial health · 2025

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

Who owns NBH UTVIKLING AS?

TELLE GRUPPEN AS
NBH UTVIKLING AS
NOK 2.5m rev. · NOK 1.9m profit

NBH UTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NBH UTVIKLING AS er morselskap for 29 datterselskaper:

Frequently asked questions about NBH UTVIKLING AS

Who owns NBH UTVIKLING AS?

TELLE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of NBH UTVIKLING AS?

NBH UTVIKLING AS had revenue of NOK 2.5m in 2025.

Where is NBH UTVIKLING AS based?

NBH UTVIKLING AS has its business address in Fjell.

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.