BIZTRAC BETA
Intermediation service activities for freight transportation by ship

RIMSHIP AS

Org. no. 863488702 Limited company (AS) Melhus Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK −654,000
Equity NOK 8.5m
Incorporated 1992
Share capital NOK 110,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−654k kr).
  • Nylig endring 2026-04-28 Adresseendring registrert 2026-04-28.

RIMSHIP AS is registered as a limited company in Melhus, Trøndelag with organisation number 863488702. The business is classified under intermediation service activities for freight transportation by ship (NACE 52.311). The company was incorporated in 1992. Registered share capital is NOK 110,000. The company's stated purpose is: “Drive med skipsmegling befrakning, kjøp pg salg. Samt hva dermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK −654,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK −654,000
Equity
NOK 8.5m
Est. value
NOK 5.9m

Financial health · 2025

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

Who owns RIMSHIP AS?

RIMCHART AS
RIMSHIP AS
NOK 3.3m rev. · NOK −654,000 profit

RIMSHIP AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIMSHIP AS

Who owns RIMSHIP AS?

RIMCHART AS is the largest registered owner, with 65.0%.

What is the revenue of RIMSHIP AS?

RIMSHIP AS had revenue of NOK 3.3m in 2025.

Who is the general manager of RIMSHIP AS?

Kjetil Rimolsrønning is registered as general manager of RIMSHIP AS.

Where is RIMSHIP AS based?

RIMSHIP AS has its business address in Gimse.

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.