BIZTRAC BETA
Uoppgitt

MOGENS AS

Org. no. 831514892 Limited company (AS) Horten Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK 139,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

MOGENS AS is registered as a limited company in Horten, Vestfold with organisation number 831514892. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen investering i aksjer og verdipapirer 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 −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 139,000
Est. value
NOK 445,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 MOGENS AS?

KRISTIAN MORTENSEN
MOGENS AS
NOK 0 rev. · NOK −11,000 profit

MOGENS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MOGENS AS own?

MOGENS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOGENS AS

Who owns MOGENS AS?

KRISTIAN MORTENSEN is the largest registered owner, with 100.0%.

What is the revenue of MOGENS AS?

MOGENS AS had revenue of NOK 0 in 2025.

Who is the general manager of MOGENS AS?

Kristian Mortensen is registered as general manager of MOGENS AS.

Where is MOGENS AS based?

MOGENS AS has its business address in Horten.

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.