BIZTRAC BETA
Accounting and bookkeeping

STAUD GRUPPEN AS

Org. no. 931913263 Limited company (AS) Sandefjord Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −963,000
Equity NOK 87.3m
Incorporated 2023
Share capital NOK 20.2m

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−963k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-07-28 Aksjekapital registrert 2026-07-28.

STAUD GRUPPEN AS is registered as a limited company in Sandefjord, Vestfold with organisation number 931913263. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 20.2m, divided into 100911907 shares. The company's stated purpose is: “Å investere i selskaper og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −963,000
Equity
NOK 87.3m
Est. value
NOK 71.7m

Financial health · 2025

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

Who owns STAUD GRUPPEN AS?

VARRO INVEST 3 AS
STAUD GRUPPEN AS
· NOK −963,000 profit

STAUD GRUPPEN AS has 18 registered shareholders:

All shareholders and roles →

Which companies does STAUD GRUPPEN AS own?

STAUD GRUPPEN AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about STAUD GRUPPEN AS

Who owns STAUD GRUPPEN AS?

VARRO INVEST 3 AS is the largest registered owner, with 58.3%.

Where is STAUD GRUPPEN AS based?

STAUD GRUPPEN AS has its business address in Sandefjord.

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.