BIZTRAC BETA
COMPANY REGISTER PROFILE
989397389 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

AUSTAD SKOG AS

Org. no. 989397389 Limited company (AS) Stor-Elvdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 9.2m
Operating profit NOK 2.2m
Equity NOK 19.2m
Incorporated 2006
Share capital NOK 600,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AUSTAD SKOG AS is registered as a limited company in Stor-Elvdal, Innlandet with organisation number 989397389. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006. Registered share capital is NOK 600,000, divided into 6 shares. The company's stated purpose is: “Drift og forvaltning av fast eiendom innenfor primærnæringene jord og skog og annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.2m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 9.2m
▲ +60 %
Operating profit
NOK 2.2m
▲ +409 %
Equity
NOK 19.2m
▲ +10 %
Est. value
NOK 18.9m

Financial health · 2025

Liquidity
8.40
Very good
Current assets ÷ current liabilities
Profitability
11.8%
Good
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns AUSTAD SKOG AS?

AUSTAD SKOG AS
NOK 9.2m rev. · NOK 2.2m profit

AUSTAD SKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUSTAD SKOG AS

Who owns AUSTAD SKOG AS?

BERINGER AS is the largest registered owner, with 100.0%.

What is the revenue of AUSTAD SKOG AS?

AUSTAD SKOG AS had revenue of NOK 9.2m in 2025.

Where is AUSTAD SKOG AS based?

AUSTAD SKOG AS has its business address in Koppang.

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.