BIZTRAC BETA
Sawmilling and planing of wood

SUSENDAL BYGDESAG AS

Org. no. 926705180 Limited company (AS) Hattfjelldal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −221,000
Equity NOK 680,000
Incorporated 2021
Share capital NOK 100,000

Signals

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

SUSENDAL BYGDESAG AS is registered as a limited company in Hattfjelldal, Nordland with organisation number 926705180. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Innehav og drift av sagbruk og høvleri, og salg av materialer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −221,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −221,000
Equity
NOK 680,000
Est. value
NOK 799,000

Financial health · 2025

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.0%
Satisfactory
Equity as a share of total capital

Who owns SUSENDAL BYGDESAG AS?

MORTEN ANDRE OLSEN
SUSENDAL BYGDESAG AS
NOK 1.2m rev. · NOK −221,000 profit

SUSENDAL BYGDESAG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SUSENDAL BYGDESAG AS

Who owns SUSENDAL BYGDESAG AS?

MORTEN ANDRE OLSEN is the largest registered owner, with 25.0%.

What is the revenue of SUSENDAL BYGDESAG AS?

SUSENDAL BYGDESAG AS had revenue of NOK 1.2m in 2025.

Who is the general manager of SUSENDAL BYGDESAG AS?

Morten Andre Olsen is registered as general manager of SUSENDAL BYGDESAG AS.

Where is SUSENDAL BYGDESAG AS based?

SUSENDAL BYGDESAG AS has its business address in Hattfjelldal.

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.