biztrac. BETA
COMPANY REGISTER PROFILE
914560624 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠NESBAK BYGG AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Construction of residential and non-residential buildings

NESBAK BYGG AS

Org. no. 914560624 Limited company (AS) Asker Incorporated 1969 In liquidation
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK 815,000
Incorporated 1969
Share capital NOK 100,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

NESBAK BYGG AS is registered as a limited company in Asker, Akershus with organisation number 914560624. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1969. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Entreprenør- og malermesterforretning, handelsvirksomhet, skog og treforedling, deltagelse i andre selskaper, eiendomsforvaltning samt kjøp og salg av fast eiendom, finansiering, utleie av driftsmidler og tjenesteyting innen regnskap og økonomi.”.

Former names: K. Nesbak Eiendom A/S

Key figures · 2025

Operating profit
NOK −38,000
▼ −10 %
Equity
NOK 815,000
▼ −32 %

Financial health · 2025

Liquidity
3.18
Very good
Current assets ÷ current liabilities
Profitability
1.2%
Weak
Return on total assets
Solidity
61.0%
Very good
Equity as a share of total capital

Who owns NESBAK BYGG AS?

NESBAK BYGG AS
· NOK −38,000 profit

NESBAK BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NESBAK BYGG AS

Who owns NESBAK BYGG AS?

Knut Nesbak is the largest registered owner, with 52.0%.

Where is NESBAK BYGG AS based?

NESBAK BYGG AS has its business address in Nesøya.

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

Report a problem

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