BIZTRAC BETA
Rental and operating of own or leased real estate

HØSSØ AS

Org. no. 993531952 Limited company (AS) Gran Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK −473,000
Incorporated 2008
Share capital NOK 2.8m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−473k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

HØSSØ AS is registered as a limited company in Gran, Innlandet with organisation number 993531952. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 2.8m, divided into 2800 shares. The company's stated purpose is: “Investering i, drift og utleie av fast eiendom, investering i aksjer og andre selskaper samt hva herved måtte stå i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK −473,000

Financial health · 2024

Liquidity
63.84
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-32.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HØSSØ AS?

BRAAUM INVEST AS
HØSSØ AS
NOK 0 rev. · NOK −24,000 profit

HØSSØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HØSSØ AS own?

HØSSØ AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HØSSØ AS

Who owns HØSSØ AS?

BRAAUM INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HØSSØ AS?

HØSSØ AS had revenue of NOK 0 in 2024.

Where is HØSSØ AS based?

HØSSØ AS has its business address in Brandbu.

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.