biztrac. BETA
COMPANY REGISTER PROFILE
913069331 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Site preparation

S.BUCK HOLDING AS

Org. no. 913069331 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −140,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−140k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).

S.BUCK HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 913069331. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer, verdipapirer og eiendom, herav også deltakelse i andre selskaper, samt annen relatert virksomhet.”.

Key figures · 2025

Operating profit
NOK −21,000
▲ +98 %
Equity
NOK −140,000
▼ −127 %

Financial health · 2025

Liquidity
-0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1057.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns S.BUCK HOLDING AS?

S.BUCK HOLDING AS
· NOK −21,000 profit

S.BUCK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.BUCK HOLDING AS own?

S.BUCK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S.BUCK HOLDING AS

Who owns S.BUCK HOLDING AS?

Stian Buck is the largest registered owner, with 100.0%.

Who is the general manager of S.BUCK HOLDING AS?

Stian Buck is registered as general manager of S.BUCK HOLDING AS.

Where is S.BUCK HOLDING AS based?

S.BUCK HOLDING AS has its business address in Blomsterdalen.

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.