BIZTRAC BETA
Other technical consultancy

JARLE RIMORK AS

Org. no. 913065212 Limited company (AS) Kongsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 893,000
Operating profit NOK 34,000
Equity NOK 44,000
Incorporated 2013
Share capital NOK 30,000

JARLE RIMORK AS is registered as a limited company in Kongsberg, Buskerud with organisation number 913065212. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med konsulentvirksomhet rettet hovedsakelig mot oljeindustrien. Kjøp, salg og utleie av fast eiendom. Kjøp, salg og utleie av anleggs- og landbruksmaskiner. Tømrervirksomhet og oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 893,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 893,000
Operating profit
NOK 34,000
Equity
NOK 44,000
Est. value
NOK 197,000

Financial health · 2025

Liquidity
1.93
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.0%
Weak
Equity as a share of total capital

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

Who owns JARLE RIMORK AS?

JARLE RIMORK
JARLE RIMORK AS
NOK 893,000 rev. · NOK 34,000 profit

JARLE RIMORK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARLE RIMORK AS

Who owns JARLE RIMORK AS?

JARLE RIMORK is the largest registered owner, with 100.0%.

What is the revenue of JARLE RIMORK AS?

JARLE RIMORK AS had revenue of NOK 893,000 in 2025.

Who is the general manager of JARLE RIMORK AS?

Jarle Rimork is registered as general manager of JARLE RIMORK AS.

Where is JARLE RIMORK AS based?

JARLE RIMORK AS has its business address in Kongsberg.

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.