biztrac. BETA
COMPANY REGISTER PROFILE
924582693 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HOFOS SKOG AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Logging

HOFOS SKOG AS

Org. no. 924582693 Limited company (AS) Våler Incorporated 2020 In liquidation
Revenue 2025 NOK 9.0m
Operating profit NOK 2.0m
Equity NOK 2.4m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

HOFOS SKOG AS is registered as a limited company in Våler, Innlandet with organisation number 924582693. The business is classified under logging (NACE 02.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forpaktning og drift av jord- og skogbrukseiendom, inklusive utvikling og drift av utmarknæring samt annen type virksomhet som naturlig hører sammen med dette, herunder deltakelse i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
▲ +65 %
Operating profit
NOK 2.0m
▲ +548 %
Equity
NOK 2.4m
▲ +3758 %

Financial health · 2025

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

Who owns HOFOS SKOG AS?

HOFOS SKOG AS
NOK 9.0m rev. · NOK 2.0m profit

HOFOS SKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOFOS SKOG AS

Who owns HOFOS SKOG AS?

Inger Berger Bjørnebye is the largest registered owner, with 100.0%.

What is the revenue of HOFOS SKOG AS?

HOFOS SKOG AS had revenue of NOK 9.0m in 2025.

Where is HOFOS SKOG AS based?

HOFOS SKOG AS has its business address in Våler I Solør.

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

Report a problem

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