BIZTRAC BETA
Site preparation

FJELLSBYGDA HYTTESERVICE AS

Org. no. 915539513 Limited company (AS) Etnedal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 250,000
Equity NOK 4.2m
Incorporated 2015
Share capital NOK 50,000

FJELLSBYGDA HYTTESERVICE AS is registered as a limited company in Etnedal, Innlandet with organisation number 915539513. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Bygge- og anleggstjenester, eiendomsutvikling, konsulenttjenester og alt som står i forbindelse med dette herunder også å eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 250,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 250,000
Equity
NOK 4.2m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns FJELLSBYGDA HYTTESERVICE AS?

KJETIL FJELD
FJELLSBYGDA HYTTESERVICE AS
NOK 2.3m rev. · NOK 250,000 profit

FJELLSBYGDA HYTTESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FJELLSBYGDA HYTTESERVICE AS own?

FJELLSBYGDA HYTTESERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FJELLSBYGDA HYTTESERVICE AS

Who owns FJELLSBYGDA HYTTESERVICE AS?

KJETIL FJELD is the largest registered owner, with 100.0%.

What is the revenue of FJELLSBYGDA HYTTESERVICE AS?

FJELLSBYGDA HYTTESERVICE AS had revenue of NOK 2.3m in 2024.

Where is FJELLSBYGDA HYTTESERVICE AS based?

FJELLSBYGDA HYTTESERVICE AS has its business address in Etnedal.

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.