BIZTRAC BETA
Rental and operating of own or leased real estate

FILEFJELL HYTTESERVICE AS

Org. no. 919139609 Limited company (AS) Lærdal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 662,000
Operating profit NOK 93,000
Equity NOK 3,000
Incorporated 2017
Share capital NOK 30,000

FILEFJELL HYTTESERVICE AS is registered as a limited company in Lærdal, Vestland with organisation number 919139609. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleige boder og lagerplass til oppbevaring av inventar, utstyr og maskiner. Formålet utover dette er hytteservice og det som naturleg høyrer til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 662,000 in revenue and NOK 93,000 in operating profit.

Key figures · 2024

Revenue
NOK 662,000
Operating profit
NOK 93,000
Equity
NOK 3,000
Est. value
NOK 136,000

Financial health · 2024

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

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

Who owns FILEFJELL HYTTESERVICE AS?

No shareholders are registered for FILEFJELL HYTTESERVICE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FILEFJELL HYTTESERVICE AS

What is the revenue of FILEFJELL HYTTESERVICE AS?

FILEFJELL HYTTESERVICE AS had revenue of NOK 662,000 in 2024.

Who is the general manager of FILEFJELL HYTTESERVICE AS?

Olav Lunden is registered as general manager of FILEFJELL HYTTESERVICE AS.

Where is FILEFJELL HYTTESERVICE AS based?

FILEFJELL HYTTESERVICE AS has its business address in Borgund.

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.