BIZTRAC BETA
Business and other management consultancy activities

AUTOEXEC AS

Org. no. 925093173 Limited company (AS) Lørenskog Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 139,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

AUTOEXEC AS is registered as a limited company in Lørenskog, Akershus with organisation number 925093173. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulenttjenester innen økonomi, administrasjon, forretningsutvikling og annet som naturlig faller sammen med dette, inkludert kjøp og salg av aksjer og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 139,000
Est. value
NOK 111,000

Financial health · 2025

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

Who owns AUTOEXEC AS?

NILS RYNNING MORK
AUTOEXEC AS
NOK 0 rev. · NOK −13,000 profit

AUTOEXEC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AUTOEXEC AS own?

AUTOEXEC AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AUTOEXEC AS

Who owns AUTOEXEC AS?

NILS RYNNING MORK is the largest registered owner, with 100.0%.

What is the revenue of AUTOEXEC AS?

AUTOEXEC AS had revenue of NOK 0 in 2025.

Where is AUTOEXEC AS based?

AUTOEXEC AS has its business address in Lørenskog.

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.