BIZTRAC BETA
Construction of residential and non-residential buildings

NADBYGG AS

Org. no. 934953037 Limited company (AS) Bamble Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK −7,000
Equity NOK −11,000
Incorporated 2025
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

NADBYGG AS is registered as a limited company in Bamble, Telemark with organisation number 934953037. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppussing, mur og betongarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK −7,000
Equity
NOK −11,000

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

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

Who owns NADBYGG AS?

ANDRZEJ KRZYSZTOF STEFANSKI
NADBYGG AS
NOK 4.7m rev. · NOK −7,000 profit

NADBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NADBYGG AS

Who owns NADBYGG AS?

ANDRZEJ KRZYSZTOF STEFANSKI is the largest registered owner, with 100.0%.

What is the revenue of NADBYGG AS?

NADBYGG AS had revenue of NOK 4.7m in 2025.

Who is the general manager of NADBYGG AS?

Andrzej Krzysztof Stefanski is registered as general manager of NADBYGG AS.

Where is NADBYGG AS based?

NADBYGG AS has its business address in Stathelle.

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.