BIZTRAC BETA
Rental and operating of own or leased real estate

BOMO AKTIVA AS

Org. no. 929440153 Limited company (AS) Snåsa Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 519,000
Operating profit NOK 386,000
Equity NOK 164,000
Incorporated 2022
Share capital NOK 30,000

BOMO AKTIVA AS is registered as a limited company in Snåsa, Trøndelag with organisation number 929440153. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive med utleie og investering i fast eiendom, og andre tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 519,000 in revenue and NOK 386,000 in operating profit.

Key figures · 2024

Revenue
NOK 519,000
Operating profit
NOK 386,000
Equity
NOK 164,000
Est. value
NOK 461,000

Financial health · 2024

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

Who owns BOMO AKTIVA AS?

OLA JAKOB BOMO
BOMO AKTIVA AS
NOK 519,000 rev. · NOK 386,000 profit

BOMO AKTIVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOMO AKTIVA AS

Who owns BOMO AKTIVA AS?

OLA JAKOB BOMO is the largest registered owner, with 100.0%.

What is the revenue of BOMO AKTIVA AS?

BOMO AKTIVA AS had revenue of NOK 519,000 in 2024.

Who is the general manager of BOMO AKTIVA AS?

Ola Jakob Bomo is registered as general manager of BOMO AKTIVA AS.

Where is BOMO AKTIVA AS based?

BOMO AKTIVA AS has its business address in Snåsa.

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.