BIZTRAC BETA
Other technical consultancy

NB29 PRO AS

Org. no. 916903804 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −134,000
Equity NOK 5.2m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−134k kr).

NB29 PRO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916903804. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av konsulenttjenester og studier innen petroleunsteknologi og prosjektering, samt handel med aksjer, andeler og verdipapirer i andre selskaper, herunder lånefinansierte investeringer med verdipapirer og valuta, eiendom og alt som naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −134,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −134,000
Equity
NOK 5.2m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns NB29 PRO AS?

SVEIN MJAALAND
NB29 PRO AS
NOK 0 rev. · NOK −134,000 profit

NB29 PRO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NB29 PRO AS own?

NB29 PRO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about NB29 PRO AS

Who owns NB29 PRO AS?

SVEIN MJAALAND is the largest registered owner, with 100.0%.

What is the revenue of NB29 PRO AS?

NB29 PRO AS had revenue of NOK 0 in 2025.

Where is NB29 PRO AS based?

NB29 PRO AS has its business address in Trondheim.

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.