BIZTRAC BETA
COMPANY REGISTER PROFILE
828716832 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

AASELIND AS

Org. no. 828716832 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 822,000
Operating profit NOK 104,000
Equity NOK 2.3m
Incorporated 2022
Share capital NOK 30,000

AASELIND AS is registered as a limited company in Oslo, Oslo with organisation number 828716832. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen konsulenttjenester og undervisning 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 822,000 in revenue and NOK 104,000 in operating profit.

Key figures · 2025

Revenue
NOK 822,000
Operating profit
NOK 104,000
Equity
NOK 2.3m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns AASELIND AS?

AASELIND HOLDING AS
AASELIND AS
NOK 822,000 rev. · NOK 104,000 profit

AASELIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AASELIND AS

Who owns AASELIND AS?

AASELIND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AASELIND AS?

AASELIND AS had revenue of NOK 822,000 in 2025.

Who is the general manager of AASELIND AS?

Åse Lindersen is registered as general manager of AASELIND AS.

Where is AASELIND AS based?

AASELIND AS has its business address in Oslo.

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.