BIZTRAC BETA
Computer programming activities

NLYTICS AS

Org. no. 936367666 Limited company (AS) Aurskog-Høland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 13,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-01.
  • Nylig endring 2026-03-18 Adresseendring registrert 2026-03-18.

NLYTICS AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 936367666. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programvare - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 13,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns NLYTICS AS?

EIRIK MOEN EILERTSEN
NLYTICS AS
NOK 0 rev. · NOK −17,000 profit

NLYTICS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about NLYTICS AS

Who owns NLYTICS AS?

EIRIK MOEN EILERTSEN is the largest registered owner, with 25.0%.

What is the revenue of NLYTICS AS?

NLYTICS AS had revenue of NOK 0 in 2025.

Where is NLYTICS AS based?

NLYTICS AS has its business address in Bjørkelangen.

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.