BIZTRAC BETA
Rental and operating of own or leased real estate

MONGSTAD BOLIG UTLEIE AS

Org. no. 928667677 Limited company (AS) Alver Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 935,000
Equity NOK 173,000
Incorporated 2022
Share capital NOK 50,000

MONGSTAD BOLIG UTLEIE AS is registered as a limited company in Alver, Vestland with organisation number 928667677. 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 50,000, divided into 500 shares. The company's stated purpose is: “Utleie og salg av boliger og hva som naturlig hører inn under dette, samt eie å investere i andre selskaper og aksjeeie.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 935,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 935,000
Equity
NOK 173,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns MONGSTAD BOLIG UTLEIE AS?

BMES INVEST AS
MONGSTAD BOLIG UTLEIE AS
NOK 1.8m rev. · NOK 935,000 profit

MONGSTAD BOLIG UTLEIE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about MONGSTAD BOLIG UTLEIE AS

Who owns MONGSTAD BOLIG UTLEIE AS?

BMES INVEST AS is the largest registered owner, with 33.0%.

What is the revenue of MONGSTAD BOLIG UTLEIE AS?

MONGSTAD BOLIG UTLEIE AS had revenue of NOK 1.8m in 2024.

Who is the general manager of MONGSTAD BOLIG UTLEIE AS?

Eivind Tveiten is registered as general manager of MONGSTAD BOLIG UTLEIE AS.

Where is MONGSTAD BOLIG UTLEIE AS based?

MONGSTAD BOLIG UTLEIE AS has its business address in Bøvågen.

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.