biztrac. BETA
COMPANY REGISTER PROFILE
914823226 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other personal service activities n.e.c.

ABELN CONSULTING AS

Org. no. 914823226 Limited company (AS) Aure Incorporated 2015 Active
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 18,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

ABELN CONSULTING AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 914823226. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulent- og flyvertjenester og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▼ −585 %
Equity
NOK 18,000
▼ −47 %
Est. value
NOK 23,000

Financial health · 2025

Liquidity
7.10
Very good
Current assets ÷ current liabilities
Profitability
-48.7%
Not satisfactory
Return on total assets
Solidity
85.9%
Weak
Equity as a share of total capital

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

Who owns ABELN CONSULTING AS?

ABELN CONSULTING AS
NOK 0 rev. · NOK −14,000 profit

ABELN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ABELN CONSULTING AS

Who owns ABELN CONSULTING AS?

Marcus Henricus Lambertus Abeln is the largest registered owner, with 100.0%.

What is the revenue of ABELN CONSULTING AS?

ABELN CONSULTING AS had revenue of NOK 0 in 2025.

Where is ABELN CONSULTING AS based?

ABELN CONSULTING AS has its business address in Mjosundet.

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.