BIZTRAC BETA
Support services to forestry

SIGMUND BERGAN AS

Org. no. 982403413 Limited company (AS) Krødsherad Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK 4.9m
Equity NOK 16.0m
Incorporated 2000
Employees 5
Share capital NOK 500,000

SIGMUND BERGAN AS is registered as a limited company in Krødsherad, Buskerud with organisation number 982403413. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2000 and has 5 registered employees. Registered share capital is NOK 500,000, divided into 200 shares. The company's stated purpose is: “Skogsentreprenør, eie og drive fast eiendom samt annen virksomhet som herunder hører med.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK 4.9m in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK 4.9m
Equity
NOK 16.0m
Est. value
NOK 22.4m

Financial health · 2024

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

Who owns SIGMUND BERGAN AS?

HANS BOYE BERGAN
SIGMUND BERGAN AS
NOK 12.9m rev. · NOK 4.9m profit

SIGMUND BERGAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIGMUND BERGAN AS own?

SIGMUND BERGAN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIGMUND BERGAN AS

Who owns SIGMUND BERGAN AS?

HANS BOYE BERGAN is the largest registered owner, with 100.0%.

What is the revenue of SIGMUND BERGAN AS?

SIGMUND BERGAN AS had revenue of NOK 12.9m in 2024.

Who is the general manager of SIGMUND BERGAN AS?

Hans Boye Bergan is registered as general manager of SIGMUND BERGAN AS.

Where is SIGMUND BERGAN AS based?

SIGMUND BERGAN AS has its business address in Krøderen.

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.