biztrac. BETA
COMPANY REGISTER PROFILE
916739168 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Cutting, shaping and finishing of stone

STEINRIKET HOLDING AS

Org. no. 916739168 Limited company (AS) Tønsberg Incorporated 2016 Active
Operating profit NOK −24,000
Equity NOK 8.6m
Incorporated 2016
Share capital NOK 130,000

Signals

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

STEINRIKET HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 916739168. The business is classified under cutting, shaping and finishing of stone (NACE 23.700). The company was incorporated in 2016. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Å være holdingselskap for investering i andre selskaper samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −24,000
▲ +76 %
Equity
NOK 8.6m
▼ −21 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
–
Not available
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 STEINRIKET HOLDING AS?

STEINRIKET HOLDING AS
· NOK −24,000 profit

STEINRIKET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STEINRIKET HOLDING AS own?

STEINRIKET HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about STEINRIKET HOLDING AS

Who owns STEINRIKET HOLDING AS?

Olav Stein Angell Veglo is the largest registered owner, with 100.0%.

Who is the general manager of STEINRIKET HOLDING AS?

Olav Stein Angell Veglo is registered as general manager of STEINRIKET HOLDING AS.

Where is STEINRIKET HOLDING AS based?

STEINRIKET HOLDING AS has its business address in Tønsberg.

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.