BIZTRAC BETA
Buying and selling of own real estate

J RØNNING INVEST AS

Org. no. 989482319 Limited company (AS) Eidskog Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −47,000
Equity NOK 6.2m
Incorporated 2006
Share capital NOK 100,000

Signals

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

J RØNNING INVEST AS is registered as a limited company in Eidskog, Innlandet with organisation number 989482319. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive med kjøp og salg av eiendom, investering i andre selskap og annet som naturlig hører inn under dette.”.

Key figures · 2024

Operating profit
NOK −47,000
Equity
NOK 6.2m
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns J RØNNING INVEST AS?

JONAS PAUL-ERIK RØNNING
J RØNNING INVEST AS
· NOK −47,000 profit

J RØNNING INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J RØNNING INVEST AS own?

J RØNNING INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about J RØNNING INVEST AS

Who owns J RØNNING INVEST AS?

JONAS PAUL-ERIK RØNNING is the largest registered owner, with 100.0%.

Who is the general manager of J RØNNING INVEST AS?

Jonas Paul-Erik Rønning is registered as general manager of J RØNNING INVEST AS.

Where is J RØNNING INVEST AS based?

J RØNNING INVEST AS has its business address in Skotterud.

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.