BIZTRAC BETA
Other non-specialised retail sale

COREPEX AS

Org. no. 898226522 Limited company (AS) Bergen Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2012
Share capital NOK 1.3m

COREPEX AS is registered as a limited company in Bergen, Vestland with organisation number 898226522. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2012. Registered share capital is NOK 1.3m, divided into 30000000 shares. The company's stated purpose is: “Postordre/internetthandel, agenturhandel, engroshandel med bredt vareutvalg, samt hva som står i forbindelse hermed. Oppføring av bygninger, rehabilitering av bygninger, kjøp og salg av eiendom, samt hva som står i forbindelse hermed. Butikkhandel med klær, samt hva som står her i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns COREPEX AS?

FREDRIK HOLM NILSEN
COREPEX AS
NOK 0 rev. · NOK 0 profit

COREPEX AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about COREPEX AS

Who owns COREPEX AS?

FREDRIK HOLM NILSEN is the largest registered owner, with 48.0%.

What is the revenue of COREPEX AS?

COREPEX AS had revenue of NOK 0 in 2024.

Who is the general manager of COREPEX AS?

Fredrik Holm Nilsen is registered as general manager of COREPEX AS.

Where is COREPEX AS based?

COREPEX AS has its business address in Laksevåg.

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.