BIZTRAC BETA
Rental and operating of own or leased real estate

TIMBER EIENDOM AS

Org. no. 983458181 Limited company (AS) Stavanger Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 6.6m
Operating profit NOK 3.6m
Equity NOK 17.6m
Incorporated 2001
Share capital NOK 106,000

TIMBER EIENDOM AS is registered as a limited company in Stavanger, Rogaland with organisation number 983458181. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2001. Registered share capital is NOK 106,000, divided into 106 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, vedlikehold og reparasjon av fast eiendom, samt kjøp og salg av aksjer.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.6m in revenue and NOK 3.6m in operating profit.

Key figures · 2024

Revenue
NOK 6.6m
Operating profit
NOK 3.6m
Equity
NOK 17.6m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns TIMBER EIENDOM AS?

FOGO AS
TIMBER EIENDOM AS
NOK 6.6m rev. · NOK 3.6m profit

TIMBER EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TIMBER EIENDOM AS own?

TIMBER EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TIMBER EIENDOM AS

Who owns TIMBER EIENDOM AS?

FOGO AS is the largest registered owner, with 37.7%.

What is the revenue of TIMBER EIENDOM AS?

TIMBER EIENDOM AS had revenue of NOK 6.6m in 2024.

Who is the general manager of TIMBER EIENDOM AS?

Espen Eriksen is registered as general manager of TIMBER EIENDOM AS.

Where is TIMBER EIENDOM AS based?

TIMBER EIENDOM AS has its business address in Stavanger.

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.