BIZTRAC BETA
Site preparation

ANLEGG & FJELLTEKNIKK AS

Org. no. 896619632 Limited company (AS) Haugesund Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 432,000
Equity NOK 1.2m
Incorporated 2011
Employees 5
Share capital NOK 197,000

ANLEGG & FJELLTEKNIKK AS is registered as a limited company in Haugesund, Rogaland with organisation number 896619632. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 197,000, divided into 393 shares. The company's stated purpose is: “Fjellarbeider, borring, sprenging og masseforflytning, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 432,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 432,000
Equity
NOK 1.2m
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.5%
Good
Equity as a share of total capital

Who owns ANLEGG & FJELLTEKNIKK AS?

BØE HOLDING AS
ANLEGG & FJELLTEKNIKK AS
NOK 5.9m rev. · NOK 432,000 profit

ANLEGG & FJELLTEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANLEGG & FJELLTEKNIKK AS

Who owns ANLEGG & FJELLTEKNIKK AS?

BØE HOLDING AS is the largest registered owner, with 50.9%.

What is the revenue of ANLEGG & FJELLTEKNIKK AS?

ANLEGG & FJELLTEKNIKK AS had revenue of NOK 5.9m in 2025.

Who is the general manager of ANLEGG & FJELLTEKNIKK AS?

Odd Eirik Bøe is registered as general manager of ANLEGG & FJELLTEKNIKK AS.

Where is ANLEGG & FJELLTEKNIKK AS based?

ANLEGG & FJELLTEKNIKK AS has its business address in Haugesund.

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.