BIZTRAC BETA
Rental and operating of own or leased real estate

TIMREHAUGVEIEN 2 AS

Org. no. 989024167 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 11.4m
Operating profit NOK 2.9m
Equity NOK 57.5m
Incorporated 2005
Share capital NOK 12.2m

Signals

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

TIMREHAUGVEIEN 2 AS is registered as a limited company in Bergen, Vestland with organisation number 989024167. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 12.2m, divided into 112690 shares. The company's stated purpose is: “Selskapets virksomhet er selv, gjennom hel- eller deleide selskaper eller ved deltakelse i andre virksomheter, å forestå kjøp, salg, eie og leie ut fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.4m in revenue and NOK 2.9m in operating profit.

Key figures · 2024

Revenue
NOK 11.4m
Operating profit
NOK 2.9m
Equity
NOK 57.5m
Est. value
NOK 44.3m

Financial health · 2024

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

Who owns TIMREHAUGVEIEN 2 AS?

HOLMS UTVIKLING AS
TIMREHAUGVEIEN 2 AS
NOK 11.4m rev. · NOK 2.9m profit

TIMREHAUGVEIEN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TIMREHAUGVEIEN 2 AS

Who owns TIMREHAUGVEIEN 2 AS?

HOLMS UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of TIMREHAUGVEIEN 2 AS?

TIMREHAUGVEIEN 2 AS had revenue of NOK 11.4m in 2024.

Where is TIMREHAUGVEIEN 2 AS based?

TIMREHAUGVEIEN 2 AS has its business address in Bergen.

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.