BIZTRAC BETA
Wholesale of information and communication equipment

NORLINK AS

Org. no. 967174092 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 504,000
Operating profit NOK 139,000
Equity NOK 8,000
Incorporated 1993
Share capital NOK 660,000

NORLINK AS is registered as a limited company in Oslo, Oslo with organisation number 967174092. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 1993. Registered share capital is NOK 660,000, divided into 660 shares. The company's stated purpose is: “Handelsvirksomhet, deltagelse i annen virksomhet samt det som naturlig faller inn under slik virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 504,000 in revenue and NOK 139,000 in operating profit.

Key figures · 2024

Revenue
NOK 504,000
Operating profit
NOK 139,000
Equity
NOK 8,000
Est. value
NOK 163,000

Financial health · 2024

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

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

Who owns NORLINK AS?

ELISABETH GILROY BØGH
NORLINK AS
NOK 504,000 rev. · NOK 139,000 profit

NORLINK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NORLINK AS own?

NORLINK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORLINK AS

Who owns NORLINK AS?

ELISABETH GILROY BØGH is the largest registered owner, with 50.0%.

What is the revenue of NORLINK AS?

NORLINK AS had revenue of NOK 504,000 in 2024.

Who is the general manager of NORLINK AS?

Bernt Runar Bøgh is registered as general manager of NORLINK AS.

Where is NORLINK AS based?

NORLINK AS has its business address in Oslo.

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.