biztrac. BETA
COMPANY REGISTER PROFILE
971075724 ORG. NO. 2022 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Silviculture and other forestry activities

LIERFOSS TYNNINGSDRIFT MIKKELRUD

Org. no. 971075724 Sole proprietorship (ENK) Aurskog-Høland Active
Ownership graph ↗
Revenue 2022 NOK 1.3m
Operating profit NOK 240,000
Equity NOK −1.3m

Signals

1 flags
  • Negativ egenkapital 2022 Bokført egenkapital er negativ (−1,3 mill kr).

LIERFOSS TYNNINGSDRIFT MIKKELRUD is registered as a sole proprietorship in Aurskog-Høland, Akershus with organisation number 971075724. The business is classified under silviculture and other forestry activities (NACE 02.100). The most recent filed accounts, for the 2022 financial year, show NOK 1.3m in revenue and NOK 240,000 in operating profit.

Former names: LIERFOSS TYNNINGSDRIFT Oddgeir Mikkelrud, ODDGEIR MIKKELRUD

Key figures · 2022

Revenue
NOK 1.3m
Operating profit
NOK 240,000
Equity
NOK −1.3m
Est. value
NOK 988,000

Financial health · 2022

Liquidity
0.50
Not satisfactory
Current assets ÷ current liabilities
Profitability
36.7%
Very good
Return on total assets
Solidity
-98.0%
Weak
Equity as a share of total capital

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

Who owns LIERFOSS TYNNINGSDRIFT MIKKELRUD?

No shareholders are registered for LIERFOSS TYNNINGSDRIFT MIKKELRUD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LIERFOSS TYNNINGSDRIFT MIKKELRUD

What is the revenue of LIERFOSS TYNNINGSDRIFT MIKKELRUD?

LIERFOSS TYNNINGSDRIFT MIKKELRUD had revenue of NOK 1.3m in 2022.

Who is the general manager of LIERFOSS TYNNINGSDRIFT MIKKELRUD?

Oddgeir Mikkelrud is registered as general manager of LIERFOSS TYNNINGSDRIFT MIKKELRUD.

Where is LIERFOSS TYNNINGSDRIFT MIKKELRUD based?

LIERFOSS TYNNINGSDRIFT MIKKELRUD has its business address in Aurskog.

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.