biztrac. BETA
COMPANY REGISTER PROFILE
935227968 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

R K UTLEIE AS

Org. no. 935227968 Limited company (AS) Melhus Incorporated 2025 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 111,000
Equity NOK 90,000
Incorporated 2025
Share capital NOK 223,000

R K UTLEIE AS is registered as a limited company in Melhus, Trøndelag with organisation number 935227968. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 223,000, divided into 22250 shares. The company's stated purpose is: “Drive utleie av maskiner og personell, samt å drive godstransport på vei. Import, eksport og varehandel annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 111,000 in operating profit.

Former names: AFAS 040325-11 AS

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 111,000
Equity
NOK 90,000
Est. value
NOK 293,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
6.9%
Weak
Equity as a share of total capital

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

Who owns R K UTLEIE AS?

R K UTLEIE AS
NOK 1.2m rev. · NOK 111,000 profit

R K UTLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about R K UTLEIE AS

Who owns R K UTLEIE AS?

Rolf Risvik is the largest registered owner, with 100.0%.

What is the revenue of R K UTLEIE AS?

R K UTLEIE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of R K UTLEIE AS?

Rolf Risvik is registered as general manager of R K UTLEIE AS.

Where is R K UTLEIE AS based?

R K UTLEIE AS has its business address in Melhus.

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

Report a problem

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