BIZTRAC BETA
Rental and operating of own or leased real estate

BEBELMA INVEST AS

Org. no. 933437345 Limited company (AS) Åsnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 694,000
Operating profit NOK 214,000
Equity NOK 210,000
Incorporated 2024
Share capital NOK 30,000

BEBELMA INVEST AS is registered as a limited company in Åsnes, Innlandet with organisation number 933437345. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering, salg og utleie av fast eiendom og utstyr, samt alt som herved står i forbindelse med dette, herunder deltakelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 694,000 in revenue and NOK 214,000 in operating profit.

Key figures · 2025

Revenue
NOK 694,000
Operating profit
NOK 214,000
Equity
NOK 210,000
Est. value
NOK 555,000

Financial health · 2025

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

Who owns BEBELMA INVEST AS?

MALIN ROMITA TRYGGVASON
BEBELMA INVEST AS
NOK 694,000 rev. · NOK 214,000 profit

BEBELMA INVEST AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BEBELMA INVEST AS

Who owns BEBELMA INVEST AS?

MALIN ROMITA TRYGGVASON is the largest registered owner, with 35.0%.

What is the revenue of BEBELMA INVEST AS?

BEBELMA INVEST AS had revenue of NOK 694,000 in 2025.

Who is the general manager of BEBELMA INVEST AS?

Malin Romita Tryggvason is registered as general manager of BEBELMA INVEST AS.

Where is BEBELMA INVEST AS based?

BEBELMA INVEST AS has its business address in Gjesåsen.

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.