BIZTRAC BETA
Repair and maintenance of motor vehicles

RITEK HOLDING AS

Org. no. 922290865 Limited company (AS) Levanger Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −172,000
Equity NOK 9.9m
Incorporated 2019
Share capital NOK 4.5m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−172k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RITEK HOLDING AS is registered as a limited company in Levanger, Trøndelag with organisation number 922290865. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2019. Registered share capital is NOK 4.5m, divided into 4412 shares. The company's stated purpose is: “Forvalte kapitalen i konsernet Ritek gjennom å eie aksjer i datterselskaper. Selskapet kan også delta i annen lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −172,000
Equity
NOK 9.9m
Est. value
NOK 13.9m

Financial health · 2025

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

Who owns RITEK HOLDING AS?

SYSTEM ENGINEERING SOLUTIONS 37 AB
RITEK HOLDING AS
· NOK −172,000 profit

RITEK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RITEK HOLDING AS own?

RITEK HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RITEK HOLDING AS

Who owns RITEK HOLDING AS?

SYSTEM ENGINEERING SOLUTIONS 37 AB is the largest registered owner, with 100.0%.

Who is the general manager of RITEK HOLDING AS?

Jan Marius Reppe is registered as general manager of RITEK HOLDING AS.

Where is RITEK HOLDING AS based?

RITEK HOLDING AS has its business address in Levanger.

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.