BIZTRAC BETA
Repair and maintenance of machinery

RS SERVICE AS

Org. no. 913477065 Limited company (AS) Stjørdal Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK −74,000
Equity NOK −2.0m
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,0 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−74k kr).

RS SERVICE AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 913477065. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Service, sakkyndig kontroll av adkomstsystemer og maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK −74,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK −74,000
Equity
NOK −2.0m

Financial health · 2024

Liquidity
0.43
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-242.2%
Weak
Equity as a share of total capital

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

Who owns RS SERVICE AS?

B155 HOLDING AS
RS SERVICE AS
NOK 4.4m rev. · NOK −74,000 profit

RS SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RS SERVICE AS

Who owns RS SERVICE AS?

B155 HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RS SERVICE AS?

RS SERVICE AS had revenue of NOK 4.4m in 2025.

Who is the general manager of RS SERVICE AS?

Tomas Eystein Foosnæs is registered as general manager of RS SERVICE AS.

Where is RS SERVICE AS based?

RS SERVICE AS has its business address in Skatval.

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.