BIZTRAC BETA
COMPANY REGISTER PROFILE
923401849 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Rental and leasing of cars and light motor vehicles

MSA BILUTLEIE AS

Org. no. 923401849 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 20.7m
Operating profit NOK 2.7m
Equity NOK 3.7m
Incorporated 2019
Share capital NOK 45,000

MSA BILUTLEIE AS is registered as a limited company in Oslo, Oslo with organisation number 923401849. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2019. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Utleie av biler, samt handelsvirksomhet herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.7m in revenue and NOK 2.7m in operating profit.

Former names: MSA AS, BRYN HELSFYR BILUTLEIE AS

Key figures · 2025

Revenue
NOK 20.7m
▼ −10 %
Operating profit
NOK 2.7m
▲ +32 %
Equity
NOK 3.7m
▲ +144 %
Est. value
NOK 12.5m

Financial health · 2025

Liquidity
1.25
Satisfactory
Current assets ÷ current liabilities
Profitability
40.2%
Very good
Return on total assets
Solidity
50.7%
Very good
Equity as a share of total capital

Who owns MSA BILUTLEIE AS?

MSA BILUTLEIE AS
NOK 20.7m rev. · NOK 2.7m profit

MSA BILUTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MSA BILUTLEIE AS

Who owns MSA BILUTLEIE AS?

MSA AS is the largest registered owner, with 66.7%.

What is the revenue of MSA BILUTLEIE AS?

MSA BILUTLEIE AS had revenue of NOK 20.7m in 2025.

Who is the general manager of MSA BILUTLEIE AS?

Mats Sandviken Andersen is registered as general manager of MSA BILUTLEIE AS.

Where is MSA BILUTLEIE AS based?

MSA BILUTLEIE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.