BIZTRAC BETA
Rental and operating of own or leased real estate

KM RENTALS AS

Org. no. 930519278 Limited company (AS) Rælingen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 694,000
Operating profit NOK 151,000
Equity NOK 73,000
Incorporated 2022
Share capital NOK 30,000

KM RENTALS AS is registered as a limited company in Rælingen, Akershus with organisation number 930519278. 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: “Selskapet skal selge tjenester innen korttidsutleie av bolig - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 694,000 in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 694,000
Operating profit
NOK 151,000
Equity
NOK 73,000
Est. value
NOK 408,000

Financial health · 2025

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

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

Who owns KM RENTALS AS?

KRISTIAN MOE
KM RENTALS AS
NOK 694,000 rev. · NOK 151,000 profit

KM RENTALS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KM RENTALS AS

Who owns KM RENTALS AS?

KRISTIAN MOE is the largest registered owner, with 100.0%.

What is the revenue of KM RENTALS AS?

KM RENTALS AS had revenue of NOK 694,000 in 2025.

Who is the general manager of KM RENTALS AS?

Kristian Moe is registered as general manager of KM RENTALS AS.

Where is KM RENTALS AS based?

KM RENTALS AS has its business address in Rælingen.

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.