BIZTRAC BETA
COMPANY REGISTER PROFILE
936208436 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

BAUG HOLDING AS

Org. no. 936208436 Limited company (AS) Tysvær Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −34,000
Equity NOK 1.5m
Incorporated 2025
Share capital NOK 30,000

Signals

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

BAUG HOLDING AS is registered as a limited company in Tysvær, Rogaland with organisation number 936208436. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Eie av aksjer og investeringsprodukter.”.

Key figures · 2025

Operating profit
NOK −34,000
Equity
NOK 1.5m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns BAUG HOLDING AS?

BAUG HOLDING AS
· NOK −34,000 profit

BAUG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BAUG HOLDING AS own?

BAUG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BAUG HOLDING AS

Who owns BAUG HOLDING AS?

TORBJØRN BAUG is the largest registered owner, with 100.0%.

Where is BAUG HOLDING AS based?

BAUG HOLDING AS has its business address in Aksdal.

Property

Business address Førlandsvegen 172, 5570 Aksdal
Cadastral unit 1146-17/48/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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