BIZTRAC BETA
Sawmilling and planing of wood

BONDEHÆREN AS

Org. no. 926713922 Limited company (AS) Sauda Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 406,000
Operating profit NOK 99,000
Equity NOK 73,000
Incorporated 2021
Share capital NOK 30,000

BONDEHÆREN AS is registered as a limited company in Sauda, Rogaland with organisation number 926713922. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilleggsnæring til eigerane sine gardsbruk. Herunder foredling og sal av eige og lokalt skogsvirke med tømmersag og tilhøyrande utstyr. Samt utleige av ledig bygningsmasse og anna som naturlig fell saman med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 406,000 in revenue and NOK 99,000 in operating profit.

Key figures · 2025

Revenue
NOK 406,000
Operating profit
NOK 99,000
Equity
NOK 73,000
Est. value
NOK 273,000

Financial health · 2024

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

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

Who owns BONDEHÆREN AS?

SVERRE GUSTAV BIRKELAND
BONDEHÆREN AS
NOK 406,000 rev. · NOK 99,000 profit

BONDEHÆREN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BONDEHÆREN AS own?

BONDEHÆREN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BONDEHÆREN AS

Who owns BONDEHÆREN AS?

SVERRE GUSTAV BIRKELAND is the largest registered owner, with 50.0%.

What is the revenue of BONDEHÆREN AS?

BONDEHÆREN AS had revenue of NOK 406,000 in 2025.

Where is BONDEHÆREN AS based?

BONDEHÆREN AS has its business address in Sauda.

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.