BIZTRAC BETA
COMPANY REGISTER PROFILE
830078282 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

RAMM INVEST AS

Org. no. 830078282 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 291,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

RAMM INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 830078282. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringsselskap.”.

Key figures · 2025

Operating profit
NOK −10,000
▼ −54 %
Equity
NOK 291,000
▲ +34 %
Est. value
NOK 643,000

Financial health · 2025

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

Who owns RAMM INVEST AS?

RAMM INVEST AS
· NOK −10,000 profit

RAMM INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAMM INVEST AS own?

RAMM INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAMM INVEST AS

Who owns RAMM INVEST AS?

KRISTOFFER RAMM is the largest registered owner, with 100.0%.

Where is RAMM INVEST AS based?

RAMM INVEST AS has its business address in Bekkestua.

Property

Business address Ringkroken 18A, 1356 Bekkestua
Cadastral unit 3201-17/691/0/0
Building Tomannsbolig, vertikal · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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