BIZTRAC BETA
Development of building projects

NOBO UTBYGGING AS

Org. no. 998588022 Limited company (AS) Notodden Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 74,000
Operating profit NOK −1.8m
Equity NOK 176,000
Incorporated 2012
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,8 mill kr).

NOBO UTBYGGING AS is registered as a limited company in Notodden, Telemark with organisation number 998588022. 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 20 shares. The company's stated purpose is: “Kjøp og utvikling av tomter/eiendommer samt bygging av bolig/leilighetsbygg og salg av disse. Selskapet kan også levere andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 74,000 in revenue and NOK −1.8m in operating profit.

Key figures · 2024

Revenue
NOK 74,000
Operating profit
NOK −1.8m
Equity
NOK 176,000
Est. value
NOK 231,000

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.0%
Weak
Equity as a share of total capital

Who owns NOBO UTBYGGING AS?

NOTODDEN BOLIGBYGGELAG
NOBO UTBYGGING AS
NOK 74,000 rev. · NOK −1.8m profit

NOBO UTBYGGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NOBO UTBYGGING AS

Who owns NOBO UTBYGGING AS?

NOTODDEN BOLIGBYGGELAG is the largest registered owner, with 100.0%.

What is the revenue of NOBO UTBYGGING AS?

NOBO UTBYGGING AS had revenue of NOK 74,000 in 2024.

Where is NOBO UTBYGGING AS based?

NOBO UTBYGGING AS has its business address in Notodden.

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.