BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

HØGÅS EIENDOM AS

Org. no. 929016157 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 276,000
Equity NOK 9.6m
Incorporated 2022
Share capital NOK 10.0m

HØGÅS EIENDOM AS is registered as a limited company in Tønsberg, Vestfold with organisation number 929016157. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2022. Registered share capital is NOK 10.0m, divided into 10002 shares. The company's stated purpose is: “Massemottak/mellomlagring herunder produksjon og salg av stein, asfalt og andre produkter, utvikling/salg og drift/utleie av næringseiendommer samt tilknyttet aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 276,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 276,000
Equity
NOK 9.6m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns HØGÅS EIENDOM AS?

HASLESTAD EIENDOM AS
HØGÅS EIENDOM AS
NOK 5.0m rev. · NOK 276,000 profit

HØGÅS EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HØGÅS EIENDOM AS

Who owns HØGÅS EIENDOM AS?

HASLESTAD EIENDOM AS is the largest registered owner, with 75.0%.

What is the revenue of HØGÅS EIENDOM AS?

HØGÅS EIENDOM AS had revenue of NOK 5.0m in 2024.

Who is the general manager of HØGÅS EIENDOM AS?

Martin Bruserud is registered as general manager of HØGÅS EIENDOM AS.

Where is HØGÅS EIENDOM AS based?

HØGÅS EIENDOM AS has its business address in Nykirke.

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.