BIZTRAC BETA
COMPANY REGISTER PROFILE
927518317 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

T.HAUGE AS

Org. no. 927518317 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK 4,000
Equity NOK 150,000
Incorporated 2021
Share capital NOK 30,000

T.HAUGE AS is registered as a limited company in Bergen, Vestland with organisation number 927518317. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer, andre selskapsandeler og verdipapirer, og alt som står i naturlig sammenheng med dette. Samt kjøp, salg og utleie av fast eiendom. Konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
Operating profit
NOK 4,000
Equity
NOK 150,000
Est. value
NOK 115,000

Financial health · 2025

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

Who owns T.HAUGE AS?

TORGEIR HILDE HAUGE
T.HAUGE AS
NOK 10,000 rev. · NOK 4,000 profit

T.HAUGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about T.HAUGE AS

Who owns T.HAUGE AS?

TORGEIR HILDE HAUGE is the largest registered owner, with 100.0%.

What is the revenue of T.HAUGE AS?

T.HAUGE AS had revenue of NOK 10,000 in 2025.

Who is the general manager of T.HAUGE AS?

Torgeir Hilde Hauge is registered as general manager of T.HAUGE AS.

Where is T.HAUGE AS based?

T.HAUGE AS has its business address in Eidsvågneset.

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.