biztrac. BETA
COMPANY REGISTER PROFILE
831039922 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Web search portal activities

ENLIST AS

Org. no. 831039922 Limited company (AS) Nes Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 31,000
Operating profit NOK 24,000
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

ENLIST AS is registered as a limited company in Nes, Akershus with organisation number 831039922. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Enlist leverer informasjon om norske virksomheter, som blant annet inkluderer regnskapstall og aksjonærinformasjon. Videre tilbyr Enlist en plattform for markedsføring av virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 31,000 in revenue and NOK 24,000 in operating profit.

Former names: MYRSETH EIENDOM AS

Key figures · 2025

Revenue
NOK 31,000
▲ +1788 %
Operating profit
NOK 24,000
▲ +541 %
Equity
NOK 18,000
▲ +4372 %
Est. value
NOK 33,000

Financial health · 2025

Liquidity
3.03
Very good
Current assets ÷ current liabilities
Profitability
55.4%
Very good
Return on total assets
Solidity
31.9%
Weak
Equity as a share of total capital

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

Who owns ENLIST AS?

ENLIST AS
NOK 31,000 rev. · NOK 24,000 profit

ENLIST AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ENLIST AS er morselskap for 6 datterselskaper:

Frequently asked questions about ENLIST AS

Who owns ENLIST AS?

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

What is the revenue of ENLIST AS?

ENLIST AS had revenue of NOK 31,000 in 2025.

Where is ENLIST AS based?

ENLIST AS has its business address in Årnes.

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.