BIZTRAC BETA
Rental and operating of own or leased real estate

FAGERLIA FRITID AS

Org. no. 929029798 Limited company (AS) Stjørdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −417,000
Equity NOK 119,000
Incorporated 2022
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−417k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FAGERLIA FRITID AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 929029798. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utleie, oppføring og forvaltning av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −417,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −417,000
Equity
NOK 119,000
Est. value
NOK 4.5m

Financial health · 2025

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

Who owns FAGERLIA FRITID AS?

BRØDRENE HOFSTAD HOLDING AS
FAGERLIA FRITID AS
NOK 2.9m rev. · NOK −417,000 profit

FAGERLIA FRITID AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FAGERLIA FRITID AS

Who owns FAGERLIA FRITID AS?

BRØDRENE HOFSTAD HOLDING AS is the largest registered owner, with 91.0%.

What is the revenue of FAGERLIA FRITID AS?

FAGERLIA FRITID AS had revenue of NOK 2.9m in 2024.

Where is FAGERLIA FRITID AS based?

FAGERLIA FRITID AS has its business address in Stjørdal.

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.