BIZTRAC BETA
Freight transport by road

RENTABILITET AS

Org. no. 999599982 Limited company (AS) Øvre Eiker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 234,000
Equity NOK 953,000
Incorporated 2013
Share capital NOK 30,000

RENTABILITET AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 999599982. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendom, samt utleie og drift av eiendom. Konsulenttjenester og andre oppdrag. Kjøp og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 234,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 234,000
Equity
NOK 953,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns RENTABILITET AS?

VEGARD DRANGE YSTENÆS
RENTABILITET AS
NOK 1.0m rev. · NOK 234,000 profit

RENTABILITET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RENTABILITET AS own?

RENTABILITET AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RENTABILITET AS

Who owns RENTABILITET AS?

VEGARD DRANGE YSTENÆS is the largest registered owner, with 100.0%.

What is the revenue of RENTABILITET AS?

RENTABILITET AS had revenue of NOK 1.0m in 2025.

Who is the general manager of RENTABILITET AS?

Vegard Drange Ystenæs is registered as general manager of RENTABILITET AS.

Where is RENTABILITET AS based?

RENTABILITET AS has its business address in Hokksund.

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.