BIZTRAC BETA
Rental and operating of own or leased real estate

FJELLBYGG ÅL AS

Org. no. 989099469 Limited company (AS) Ål Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 1.0m
Equity NOK 159,000
Incorporated 2005
Employees 5
Share capital NOK 100,000

FJELLBYGG ÅL AS is registered as a limited company in Ål, Buskerud with organisation number 989099469. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av faste eiendommer, snekkervirksomhet, byggevareutsalg, kjøp og salg av motorkjøretøyer og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 1.0m
Equity
NOK 159,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

Who owns FJELLBYGG ÅL AS?

ARNEGARD HOLDING AS
FJELLBYGG ÅL AS
NOK 6.2m rev. · NOK 1.0m profit

FJELLBYGG ÅL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELLBYGG ÅL AS

Who owns FJELLBYGG ÅL AS?

ARNEGARD HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of FJELLBYGG ÅL AS?

FJELLBYGG ÅL AS had revenue of NOK 6.2m in 2025.

Who is the general manager of FJELLBYGG ÅL AS?

Odd Kåre Tveito Skjervheim is registered as general manager of FJELLBYGG ÅL AS.

Where is FJELLBYGG ÅL AS based?

FJELLBYGG ÅL AS has its business address in Ål.

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.