BIZTRAC BETA
Other captive investment companies

J/R HOLDING AS

Org. no. 919566981 Limited company (AS) Fredrikstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 21.9m
Incorporated 2017
Share capital NOK 72,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

J/R HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 919566981. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 72,000, divided into 200 shares. The company's stated purpose is: “Investeringsselskap, herunder investering i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 21.9m
Est. value
NOK 14.8m

Financial health · 2025

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

Who owns J/R HOLDING AS?

JOHNNY RANGJORD
J/R HOLDING AS
NOK 0 rev. · NOK −19,000 profit

J/R HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J/R HOLDING AS

Who owns J/R HOLDING AS?

JOHNNY RANGJORD is the largest registered owner, with 100.0%.

What is the revenue of J/R HOLDING AS?

J/R HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of J/R HOLDING AS?

Johnny Rangjord is registered as general manager of J/R HOLDING AS.

Where is J/R HOLDING AS based?

J/R HOLDING AS has its business address in Gressvik.

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.