biztrac. BETA
COMPANY REGISTER PROFILE
988465119 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Other business support service activities n.e.c.

INLINK AS

Org. no. 988465119 Limited company (AS) Lillestrøm Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK −430,000
Incorporated 2005
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−430k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

INLINK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 988465119. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å forestå sikker oppbevaring av to eiendeler.”.

Former names: INTERANCE UTVIKLING AS, TRYGGFORSIKRING UTVIKLING AS, MIPOS TECHNOLOGY AS

Key figures · 2025

Operating profit
NOK −16,000
▼ −22 %
Equity
NOK −430,000
▼ −37 %

Financial health · 2025

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
-53.9%
Weak
Equity as a share of total capital

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

Who owns INLINK AS?

INLINK AS
· NOK −16,000 profit

INLINK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INLINK AS own?

INLINK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about INLINK AS

Who owns INLINK AS?

FORSIKRINGSHUSET AS is the largest registered owner, with 100.0%.

Where is INLINK AS based?

INLINK AS has its business address in Lillestrøm.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.