BIZTRAC BETA
Rental and operating of own or leased real estate

TORGET 3 EIENDOM AS

Org. no. 914845416 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −74,000
Equity NOK 17.3m
Incorporated 2014
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−74k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TORGET 3 EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 914845416. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Besittelse og drift av fast eiendom, samt deltakelse i andre selskaper med lignende formål.”.

Key figures · 2024

Operating profit
NOK −74,000
Equity
NOK 17.3m
Est. value
NOK 15.8m

Financial health · 2024

Liquidity
3.27
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.5%
Good
Equity as a share of total capital

Who owns TORGET 3 EIENDOM AS?

FISKETORVET EIENDOM AS
TORGET 3 EIENDOM AS
· NOK −74,000 profit

TORGET 3 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TORGET 3 EIENDOM AS own?

TORGET 3 EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TORGET 3 EIENDOM AS

Who owns TORGET 3 EIENDOM AS?

FISKETORVET EIENDOM AS is the largest registered owner, with 66.0%.

Who is the general manager of TORGET 3 EIENDOM AS?

Sing Wah Hau Hui is registered as general manager of TORGET 3 EIENDOM AS.

Where is TORGET 3 EIENDOM AS based?

TORGET 3 EIENDOM 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.