BIZTRAC BETA
Repair and maintenance of machinery

RO SERVICE AS

Org. no. 934766008 Limited company (AS) Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 376,000
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RO SERVICE AS is registered as a limited company in Hå, Rogaland with organisation number 934766008. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Forestå service på anleggsmaskiner og utstyr, samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 376,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 376,000
Equity
NOK 30,000
Est. value
NOK 1.2m

Financial health · 2025

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

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

Who owns RO SERVICE AS?

RENTAL.ONE AS
RO SERVICE AS
NOK 2.4m rev. · NOK 376,000 profit

RO SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RO SERVICE AS

Who owns RO SERVICE AS?

RENTAL.ONE AS is the largest registered owner, with 100.0%.

What is the revenue of RO SERVICE AS?

RO SERVICE AS had revenue of NOK 2.4m in 2025.

Who is the general manager of RO SERVICE AS?

Kjetil Friestad is registered as general manager of RO SERVICE AS.

Where is RO SERVICE AS based?

RO SERVICE AS has its business address in Nærbø.

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.