BIZTRAC BETA
Development of building projects

3-BYGG AS

Org. no. 988586404 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −29,000
Equity NOK 1.1m
Incorporated 2005
Share capital NOK 259,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−29k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

3-BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988586404. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 259,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2025

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

Who owns 3-BYGG AS?

3 - BYGG HOLDING AS
3-BYGG AS
NOK 0 rev. · NOK −29,000 profit

3-BYGG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does 3-BYGG AS own?

3-BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about 3-BYGG AS

Who owns 3-BYGG AS?

3 - BYGG HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of 3-BYGG AS?

3-BYGG AS had revenue of NOK 0 in 2025.

Who is the general manager of 3-BYGG AS?

Per Erik Austberg is registered as general manager of 3-BYGG AS.

Where is 3-BYGG AS based?

3-BYGG AS has its business address in Heimdal.

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.