BIZTRAC BETA
COMPANY REGISTER PROFILE
911832100 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Manufacture of other fabricated metal products n.e.c.

FREKHAUG STÅL AS

Org. no. 911832100 Limited company (AS) Alver Incorporated 1955 Active
Ownership graph ↗
Revenue 2025 NOK 59.5m
Operating profit NOK 3.3m
Equity NOK 25.8m
Incorporated 1955
Employees 38
Share capital NOK 1.0m

FREKHAUG STÅL AS is registered as a limited company in Alver, Vestland with organisation number 911832100. The business is classified under manufacture of other fabricated metal products n.e.c. (NACE 25.990). The company was incorporated in 1955 and has 38 registered employees. Registered share capital is NOK 1.0m, divided into 10000 shares. The company's stated purpose is: “Fabrikkdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 59.5m in revenue and NOK 3.3m in operating profit.

Key figures · 2025

Revenue
NOK 59.5m
Operating profit
NOK 3.3m
Equity
NOK 25.8m
Est. value
NOK 26.4m

Financial health · 2025

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

Who owns FREKHAUG STÅL AS?

FREKHAUG STÅL AS has 7 registered shareholders:

All shareholders and roles →

Which companies does FREKHAUG STÅL AS own?

FREKHAUG STÅL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FREKHAUG STÅL AS

Who owns FREKHAUG STÅL AS?

JOHN VILLY SANDVIK is the largest registered owner, with 33.3%.

What is the revenue of FREKHAUG STÅL AS?

FREKHAUG STÅL AS had revenue of NOK 59.5m in 2025.

Who is the general manager of FREKHAUG STÅL AS?

Vegard Sagstad is registered as general manager of FREKHAUG STÅL AS.

Where is FREKHAUG STÅL AS based?

FREKHAUG STÅL AS has its business address in Frekhaug.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.