BIZTRAC BETA
Intermediation service activities for real estate activities

LINK NÆRINGSMEGLING AS

Org. no. 986746358 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK 98,000
Equity NOK 451,000
Incorporated 2004
Share capital NOK 100,000

LINK NÆRINGSMEGLING AS is registered as a limited company in Bærum, Akershus with organisation number 986746358. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive eiendomsmegling med spesialisering innen næringseiendom, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK 98,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK 98,000
Equity
NOK 451,000
Est. value
NOK 573,000

Financial health · 2024

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

Who owns LINK NÆRINGSMEGLING AS?

GRANBAKKEN INVEST AS
LINK NÆRINGSMEGLING AS
NOK 3.9m rev. · NOK 98,000 profit

LINK NÆRINGSMEGLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINK NÆRINGSMEGLING AS

Who owns LINK NÆRINGSMEGLING AS?

GRANBAKKEN INVEST AS is the largest registered owner, with 60.0%.

What is the revenue of LINK NÆRINGSMEGLING AS?

LINK NÆRINGSMEGLING AS had revenue of NOK 3.9m in 2024.

Who is the general manager of LINK NÆRINGSMEGLING AS?

Bjørn Sørum is registered as general manager of LINK NÆRINGSMEGLING AS.

Where is LINK NÆRINGSMEGLING AS based?

LINK NÆRINGSMEGLING AS has its business address in Fornebu.

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.