BIZTRAC BETA
Computer consultancy and computer facilities management activities

XLNS AS

Org. no. 914316944 Limited company (AS) Ullensaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 712,000
Operating profit NOK 362,000
Equity NOK 2.9m
Incorporated 2014
Share capital NOK 30,000

XLNS AS is registered as a limited company in Ullensaker, Akershus with organisation number 914316944. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Yte konsulent- og rådgivningstjenester innen IT-sektoren, utvikling av programvare, samt alt som hører naturlig til dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 712,000 in revenue and NOK 362,000 in operating profit.

Key figures · 2024

Revenue
NOK 712,000
Operating profit
NOK 362,000
Equity
NOK 2.9m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns XLNS AS?

FRANK ROBIN DANIELSEN
XLNS AS
NOK 712,000 rev. · NOK 362,000 profit

XLNS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does XLNS AS own?

XLNS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about XLNS AS

Who owns XLNS AS?

FRANK ROBIN DANIELSEN is the largest registered owner, with 100.0%.

What is the revenue of XLNS AS?

XLNS AS had revenue of NOK 712,000 in 2024.

Where is XLNS AS based?

XLNS AS has its business address in Jessheim.

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.