BIZTRAC BETA
Rental and operating of own or leased real estate

GLASSGÅRDEN AS

Org. no. 813463032 Limited company (AS) Fauske Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 681,000
Operating profit NOK −1.2m
Equity NOK 2.3m
Incorporated 2014
Share capital NOK 276,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

GLASSGÅRDEN AS is registered as a limited company in Fauske, Nordland with organisation number 813463032. 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 276,000, divided into 552582 shares. The company's stated purpose is: “Eie og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 681,000 in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 681,000
Operating profit
NOK −1.2m
Equity
NOK 2.3m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns GLASSGÅRDEN AS?

HELGE HENRIKSEN
GLASSGÅRDEN AS
NOK 681,000 rev. · NOK −1.2m profit

GLASSGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GLASSGÅRDEN AS own?

GLASSGÅRDEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about GLASSGÅRDEN AS

Who owns GLASSGÅRDEN AS?

HELGE HENRIKSEN is the largest registered owner, with 100.0%.

What is the revenue of GLASSGÅRDEN AS?

GLASSGÅRDEN AS had revenue of NOK 681,000 in 2024.

Who is the general manager of GLASSGÅRDEN AS?

Helge Henriksen is registered as general manager of GLASSGÅRDEN AS.

Where is GLASSGÅRDEN AS based?

GLASSGÅRDEN AS has its business address in Fauske.

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.