BIZTRAC BETA
Activities of employment placement agencies

LINK REKRUTTERING AS

Org. no. 980527476 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 29,000
Equity NOK 114,000
Incorporated 1999
Share capital NOK 36,000

LINK REKRUTTERING AS is registered as a limited company in Oslo, Oslo with organisation number 980527476. The business is classified under activities of employment placement agencies (NACE 78.100). The company was incorporated in 1999. Registered share capital is NOK 36,000, divided into 360 shares. The company's stated purpose is: “Salg av tjenester inne rekruttering av ledere, spesialister og rådgivning i tilknytning til dette, samt det som har naturlig tilknytning til dette, herunder å delta i andre selskaper med lignende virksomeht.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 29,000
Equity
NOK 114,000
Est. value
NOK 147,000

Financial health · 2025

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

Who owns LINK REKRUTTERING AS?

TERJE MIKAL STRØM
LINK REKRUTTERING AS
NOK 1.9m rev. · NOK 29,000 profit

LINK REKRUTTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINK REKRUTTERING AS

Who owns LINK REKRUTTERING AS?

TERJE MIKAL STRØM is the largest registered owner, with 100.0%.

What is the revenue of LINK REKRUTTERING AS?

LINK REKRUTTERING AS had revenue of NOK 1.9m in 2025.

Who is the general manager of LINK REKRUTTERING AS?

Terje Mikal Strøm is registered as general manager of LINK REKRUTTERING AS.

Where is LINK REKRUTTERING AS based?

LINK REKRUTTERING 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.