BIZTRAC BETA
Construction of residential and non-residential buildings

BIRKELUND SAGBRUK AS

Org. no. 979760612 Limited company (AS) Nordreisa Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 403,000
Operating profit NOK −504,000
Equity NOK 5.2m
Incorporated 1998
Share capital NOK 800,000

Signals

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

BIRKELUND SAGBRUK AS is registered as a limited company in Nordreisa, Troms with organisation number 979760612. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1998. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Salg av byggevarer, og derunder beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 403,000 in revenue and NOK −504,000 in operating profit.

Key figures · 2025

Revenue
NOK 403,000
Operating profit
NOK −504,000
Equity
NOK 5.2m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns BIRKELUND SAGBRUK AS?

HELGE BIRKELUND
BIRKELUND SAGBRUK AS
NOK 403,000 rev. · NOK −504,000 profit

BIRKELUND SAGBRUK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRKELUND SAGBRUK AS

Who owns BIRKELUND SAGBRUK AS?

HELGE BIRKELUND is the largest registered owner, with 100.0%.

What is the revenue of BIRKELUND SAGBRUK AS?

BIRKELUND SAGBRUK AS had revenue of NOK 403,000 in 2025.

Who is the general manager of BIRKELUND SAGBRUK AS?

Helge Birkelund is registered as general manager of BIRKELUND SAGBRUK AS.

Where is BIRKELUND SAGBRUK AS based?

BIRKELUND SAGBRUK AS has its business address in Sørkjosen.

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.