biztrac. BETA
COMPANY REGISTER PROFILE
930873071 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

NIMROD HOLDING AS

Org. no. 930873071 Limited company (AS) Oslo Incorporated 1980 Active
Ownership graph ↗
Operating profit NOK −4.4m
Equity NOK 146.9m
Incorporated 1980
Share capital NOK 2.8m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4,4 mill kr).
  • Nylig endring 2026-09-28 Aksjekapital registrert 2026-09-28.

NIMROD HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 930873071. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1980. Registered share capital is NOK 2.8m, divided into 1008 shares. The company's stated purpose is: “Investeringsvirksomhet og andre relaterte aktiviteter, samt å gi støtte til veldedige og allmennyttige formål.”.

Former names: AS TONIMA

Key figures · 2025

Operating profit
NOK −4.4m
▲ +45 %
Equity
NOK 146.9m
▲ +6 %
Est. value
NOK 132.2m

Financial health · 2025

Liquidity
1247.31
Very good
Current assets ÷ current liabilities
Profitability
9.2%
Satisfactory
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns NIMROD HOLDING AS?

NIMROD HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does NIMROD HOLDING AS own?

NIMROD HOLDING AS holds stakes in 19 companies:

See the full ownership structure →

Frequently asked questions about NIMROD HOLDING AS

Who owns NIMROD HOLDING AS?

Philip Rynning-Nielsen is the largest registered owner, with 39.8%.

Who is the general manager of NIMROD HOLDING AS?

Tore Rynning-Nielsen is registered as general manager of NIMROD HOLDING AS.

Where is NIMROD HOLDING AS based?

NIMROD HOLDING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.