BIZTRAC BETA
Repair and maintenance of machinery

ROMERIKE TRUCKSERVICE AS

Org. no. 951444774 Limited company (AS) Rælingen Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 15.7m
Operating profit NOK 428,000
Equity NOK 5.2m
Incorporated 1989
Employees 5
Share capital NOK 900,000

ROMERIKE TRUCKSERVICE AS is registered as a limited company in Rælingen, Akershus with organisation number 951444774. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1989 and has 5 registered employees. Registered share capital is NOK 900,000, divided into 150 shares. The company's stated purpose is: “Reparasjon av trucker og alt som står i forbind- else med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.7m in revenue and NOK 428,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.7m
Operating profit
NOK 428,000
Equity
NOK 5.2m
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
3.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.5%
Good
Equity as a share of total capital

Who owns ROMERIKE TRUCKSERVICE AS?

SUSANNE LINDMARK KJENNER
ROMERIKE TRUCKSERVICE AS
NOK 15.7m rev. · NOK 428,000 profit

ROMERIKE TRUCKSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROMERIKE TRUCKSERVICE AS

Who owns ROMERIKE TRUCKSERVICE AS?

SUSANNE LINDMARK KJENNER is the largest registered owner, with 100.0%.

What is the revenue of ROMERIKE TRUCKSERVICE AS?

ROMERIKE TRUCKSERVICE AS had revenue of NOK 15.7m in 2024.

Who is the general manager of ROMERIKE TRUCKSERVICE AS?

Susanne Lindmark Kjenner is registered as general manager of ROMERIKE TRUCKSERVICE AS.

Where is ROMERIKE TRUCKSERVICE AS based?

ROMERIKE TRUCKSERVICE AS has its business address in Fjerdingby.

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.