BIZTRAC BETA
Business and other management consultancy activities

LINKT AS

Org. no. 897890712 Limited company (AS) Ås Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 260,000
Operating profit NOK 124,000
Equity NOK 27,000
Incorporated 2012
Share capital NOK 30,000

LINKT AS is registered as a limited company in Ås, Akershus with organisation number 897890712. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Arrangering av sponsoraktiviteter innen kultur og idrett, med tyngde på relasjonsutvikling, salg, forretningsutvikling, prosjektledelse, kommunikasjon og aktivering. Herunder også å investere i selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 260,000 in revenue and NOK 124,000 in operating profit.

Key figures · 2024

Revenue
NOK 260,000
Operating profit
NOK 124,000
Equity
NOK 27,000
Est. value
NOK 402,000

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.4%
Weak
Equity as a share of total capital

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

Who owns LINKT AS?

CHRISTIN LILLEGREND
LINKT AS
NOK 260,000 rev. · NOK 124,000 profit

LINKT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINKT AS

Who owns LINKT AS?

CHRISTIN LILLEGREND is the largest registered owner, with 47.5%.

What is the revenue of LINKT AS?

LINKT AS had revenue of NOK 260,000 in 2024.

Who is the general manager of LINKT AS?

Rune Hansen is registered as general manager of LINKT AS.

Where is LINKT AS based?

LINKT AS has its business address in Vinterbro.

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.