BIZTRAC BETA
Manufacture of liquid biofuels

HYWOOD AS

Org. no. 932860597 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 18,000
Incorporated 2024
Share capital NOK 100,000

Signals

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

HYWOOD AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932860597. The business is classified under manufacture of liquid biofuels (NACE 20.510). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikling og drift av metanolproduksjon basert på hydrogen og trevirke og annet som naturlig hører sammen med dette. Selskapet vil også ta del i andre selskaper der dette gir et faglig og økonomisk utbytte.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 18,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns HYWOOD AS?

4FUTURE AS
HYWOOD AS
NOK 0 rev. · NOK −4,000 profit

HYWOOD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HYWOOD AS

Who owns HYWOOD AS?

4FUTURE AS is the largest registered owner, with 100.0%.

What is the revenue of HYWOOD AS?

HYWOOD AS had revenue of NOK 0 in 2025.

Who is the general manager of HYWOOD AS?

Anders Østby Kjensjord is registered as general manager of HYWOOD AS.

Where is HYWOOD AS based?

HYWOOD AS has its business address in Sørumsand.

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.