biztrac. BETA
COMPANY REGISTER PROFILE
912797252 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Non-specialised wholesale of food, beverages and tobacco

SANDVIGEN TRADING AS

Org. no. 912797252 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Operating profit NOK −150,000
Equity NOK 9.5m
Incorporated 2013
Share capital NOK 150,000

Signals

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

SANDVIGEN TRADING AS is registered as a limited company in Bærum, Akershus with organisation number 912797252. The business is classified under non-specialised wholesale of food, beverages and tobacco (NACE 46.390). The company was incorporated in 2013. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Finansiering og kapitalforvaltning. Selskapet kan også ha eierinteresser i andre selskaper av enhver art.”.

Key figures · 2025

Operating profit
NOK −150,000
▲ +11 %
Equity
NOK 9.5m
▼ −13 %
Est. value
NOK 6.0m

Financial health · 2025

Liquidity
102.76
Very good
Current assets ÷ current liabilities
Profitability
9.9%
Satisfactory
Return on total assets
Solidity
99.2%
Very good
Equity as a share of total capital

Who owns SANDVIGEN TRADING AS?

SANDVIGEN TRADING AS
· NOK −150,000 profit

SANDVIGEN TRADING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SANDVIGEN TRADING AS own?

SANDVIGEN TRADING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SANDVIGEN TRADING AS

Who owns SANDVIGEN TRADING AS?

Baard Alfred Hanssen is the largest registered owner, with 100.0%.

Who is the general manager of SANDVIGEN TRADING AS?

Baard Alfred Hanssen is registered as general manager of SANDVIGEN TRADING AS.

Where is SANDVIGEN TRADING AS based?

SANDVIGEN TRADING AS has its business address in Sandvika.

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

Report a problem

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