BIZTRAC BETA
Sawmilling and planing of wood

DALBYGDA SAG AS

Org. no. 917001049 Limited company (AS) Steinkjer Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK −720
Operating profit NOK −27,000
Equity NOK 23,000
Incorporated 2016
Share capital NOK 240,000

Signals

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

DALBYGDA SAG AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 917001049. The business is classified under sawmilling and planing of wood (NACE 16.110). The company was incorporated in 2016. Registered share capital is NOK 240,000, divided into 240 shares. The company's stated purpose is: “Saging og tilhørende virksomhet, salg, eiendomsutvikling, aksjehandel, konsulentvirksomhet og home parties.”. The most recent filed accounts, for the 2025 financial year, show NOK −720 in revenue and NOK −27,000 in operating profit.

Key figures · 2025

Revenue
NOK −720
Operating profit
NOK −27,000
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns DALBYGDA SAG AS?

KJELL MORTEN FINSTAD
DALBYGDA SAG AS
NOK −720 rev. · NOK −27,000 profit

DALBYGDA SAG AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about DALBYGDA SAG AS

Who owns DALBYGDA SAG AS?

KJELL MORTEN FINSTAD is the largest registered owner, with 16.7%.

What is the revenue of DALBYGDA SAG AS?

DALBYGDA SAG AS had revenue of NOK −720 in 2025.

Who is the general manager of DALBYGDA SAG AS?

Ove Kristoffer Almlid is registered as general manager of DALBYGDA SAG AS.

Where is DALBYGDA SAG AS based?

DALBYGDA SAG AS has its business address in Beitstad.

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.