BIZTRAC BETA
Wholesale of other machinery and equipment

PROFINOR AS

Org. no. 931664123 Limited company (AS) Bærum Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 383,000
Equity NOK 38.0m
Incorporated 1981
Share capital NOK 1.4m

PROFINOR AS is registered as a limited company in Bærum, Akershus with organisation number 931664123. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 1981. Registered share capital is NOK 1.4m, divided into 1423662 shares. The company's stated purpose is: “Fabrikasjon, handel, agentur samt annen økonomisk virksomhet, herunder å interessere seg i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 383,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 383,000
Equity
NOK 38.0m
Est. value
NOK 19.6m

Financial health · 2024

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

Who owns PROFINOR AS?

CARL ERICK FRØLICH FUGLESANG
PROFINOR AS
NOK 2.5m rev. · NOK 383,000 profit

PROFINOR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does PROFINOR AS own?

PROFINOR AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about PROFINOR AS

Who owns PROFINOR AS?

CARL ERICK FRØLICH FUGLESANG is the largest registered owner, with 63.3%.

What is the revenue of PROFINOR AS?

PROFINOR AS had revenue of NOK 2.5m in 2024.

Who is the general manager of PROFINOR AS?

Carl Erick Frølich Fuglesang is registered as general manager of PROFINOR AS.

Where is PROFINOR AS based?

PROFINOR AS has its business address in Skui.

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.