BIZTRAC BETA
Retail sale of medical and orthopaedic goods

GHØR AS

Org. no. 925559148 Limited company (AS) Gran Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 225,000
Operating profit NOK −100,000
Equity NOK −1.3m
Incorporated 2020
Share capital NOK 220,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−100k kr).

GHØR AS is registered as a limited company in Gran, Innlandet with organisation number 925559148. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2020. Registered share capital is NOK 220,000, divided into 200000 shares. The company's stated purpose is: “Salg, formidling og rådgivning av hørselsrelaterte produkter og tjenester. Deltagelse i andre selskaper av samme kategori.”. The most recent filed accounts, for the 2025 financial year, show NOK 225,000 in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 225,000
Operating profit
NOK −100,000
Equity
NOK −1.3m

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-179.1%
Weak
Equity as a share of total capital

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

Who owns GHØR AS?

LETS EIENDOM II AS
GHØR AS
NOK 225,000 rev. · NOK −100,000 profit

GHØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GHØR AS

Who owns GHØR AS?

LETS EIENDOM II AS is the largest registered owner, with 100.0%.

What is the revenue of GHØR AS?

GHØR AS had revenue of NOK 225,000 in 2025.

Who is the general manager of GHØR AS?

Terje Brunstad is registered as general manager of GHØR AS.

Where is GHØR AS based?

GHØR 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.