BIZTRAC BETA
Other support activities for transportation

RAMBERG-GRUPPEN AS

Org. no. 989107763 Limited company (AS) Holmestrand Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −243,000
Equity NOK 235.8m
Incorporated 2005
Share capital NOK 2.3m

Signals

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

RAMBERG-GRUPPEN AS is registered as a limited company in Holmestrand, Vestfold with organisation number 989107763. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 2005. Registered share capital is NOK 2.3m, divided into 600 shares. The company's stated purpose is: “Investering i fast eiendom og alt som står i forbindelse med dette herunder deltagelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −243,000
Equity
NOK 235.8m
Est. value
NOK 255.8m

Financial health · 2024

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

Who owns RAMBERG-GRUPPEN AS?

BJØRN RAMBERG INVEST AS
RAMBERG-GRUPPEN AS
· NOK −243,000 profit

RAMBERG-GRUPPEN AS has 4 registered shareholders:

All shareholders and roles →

Which companies does RAMBERG-GRUPPEN AS own?

RAMBERG-GRUPPEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about RAMBERG-GRUPPEN AS

Who owns RAMBERG-GRUPPEN AS?

BJØRN RAMBERG INVEST AS is the largest registered owner, with 68.7%.

Who is the general manager of RAMBERG-GRUPPEN AS?

Bjørn Helge Ramberg is registered as general manager of RAMBERG-GRUPPEN AS.

Where is RAMBERG-GRUPPEN AS based?

RAMBERG-GRUPPEN AS has its business address in Sande I Vestfold.

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.