BIZTRAC BETA
COMPANY REGISTER PROFILE
982825814 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Wholesale of grain, unmanufactured tobacco, seeds and animal feeds

ÅLSTADØYA FORSENTRAL DA

Org. no. 982825814 General partnership with shared liability (DA) Steigen Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 1.1m
Equity NOK 4.5m
Incorporated 2000

ÅLSTADØYA FORSENTRAL DA is registered as a general partnership with shared liability in Steigen, Nordland with organisation number 982825814. The business is classified under wholesale of grain, unmanufactured tobacco, seeds and animal feeds (NACE 46.210). The company was incorporated in 2000. The company's stated purpose is: “Selge landbruksprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 1.1m
Equity
NOK 4.5m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns ÅLSTADØYA FORSENTRAL DA?

No shareholders are registered for ÅLSTADØYA FORSENTRAL DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does ÅLSTADØYA FORSENTRAL DA own?

ÅLSTADØYA FORSENTRAL DA holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ÅLSTADØYA FORSENTRAL DA

What is the revenue of ÅLSTADØYA FORSENTRAL DA?

ÅLSTADØYA FORSENTRAL DA had revenue of NOK 8.7m in 2025.

Who is the general manager of ÅLSTADØYA FORSENTRAL DA?

Jørn Falch is registered as general manager of ÅLSTADØYA FORSENTRAL DA.

Where is ÅLSTADØYA FORSENTRAL DA based?

ÅLSTADØYA FORSENTRAL DA has its business address in Engeløya.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.