BIZTRAC BETA
Development of building projects

MASIBO AS

Org. no. 932976269 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3 kr).

MASIBO AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932976269. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og øvrige finansielle investeringer, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns MASIBO AS?

BØRGE STAMNES
MASIBO AS
NOK 0 rev. · NOK −3 profit

MASIBO AS has 3 registered shareholders:

All shareholders and roles →

Which companies does MASIBO AS own?

MASIBO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MASIBO AS

Who owns MASIBO AS?

BØRGE STAMNES is the largest registered owner, with 33.3%.

What is the revenue of MASIBO AS?

MASIBO AS had revenue of NOK 0 in 2024.

Who is the general manager of MASIBO AS?

Siri Bjerkan is registered as general manager of MASIBO AS.

Where is MASIBO AS based?

MASIBO 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.