BIZTRAC BETA
Support services to forestry

SIKRINGSHOGST AS

Org. no. 898095622 Limited company (AS) Arendal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 5,000
Equity NOK 78,000
Incorporated 2012
Share capital NOK 70,000

SIKRINGSHOGST AS is registered as a limited company in Arendal, Agder with organisation number 898095622. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2012. Registered share capital is NOK 70,000, divided into 70 shares. The company's stated purpose is: “Tjenesteytende virksomhet innen jordbruk, skogbruk og for privatpersoner og andre produkter/tjenester som naturlig hører sammen med dette . Hovedbeskjeftigelse vil i utgangspunktet være linjerydding og lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 5,000
Equity
NOK 78,000
Est. value
NOK 50,000

Financial health · 2025

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.6%
Weak
Equity as a share of total capital

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

Who owns SIKRINGSHOGST AS?

GUNNAR HAUGENES
SIKRINGSHOGST AS
NOK 2.2m rev. · NOK 5,000 profit

SIKRINGSHOGST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIKRINGSHOGST AS

Who owns SIKRINGSHOGST AS?

GUNNAR HAUGENES is the largest registered owner, with 100.0%.

What is the revenue of SIKRINGSHOGST AS?

SIKRINGSHOGST AS had revenue of NOK 2.2m in 2025.

Who is the general manager of SIKRINGSHOGST AS?

Gunnar Haugenes is registered as general manager of SIKRINGSHOGST AS.

Where is SIKRINGSHOGST AS based?

SIKRINGSHOGST AS has its business address in Kongshavn.

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.