BIZTRAC BETA
Buying and selling of own real estate

JRM SVE HOLDING AS

Org. no. 914457769 Limited company (AS) Bærum Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 1.9m
Incorporated 2014
Share capital NOK 30,000

Signals

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

JRM SVE HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 914457769. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsselskap som vil eie andeler i andres selskap og investere i andre foretak. Skal ha muligheten for at leie ut tjenester innen konsultasjon og rådgiving , samt kjøp, salg og utleie av fast eiendom og tjenester som hører til.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK 1.9m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns JRM SVE HOLDING AS?

JONNY ROY MATTIAS SVENSSON
JRM SVE HOLDING AS
· NOK −9,000 profit

JRM SVE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JRM SVE HOLDING AS own?

JRM SVE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JRM SVE HOLDING AS

Who owns JRM SVE HOLDING AS?

JONNY ROY MATTIAS SVENSSON is the largest registered owner, with 100.0%.

Who is the general manager of JRM SVE HOLDING AS?

Jonny Roy Mattias Svensson is registered as general manager of JRM SVE HOLDING AS.

Where is JRM SVE HOLDING AS based?

JRM SVE HOLDING AS has its business address in Eiksmarka.

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.