BIZTRAC BETA
Accounting and bookkeeping

JOHANSSON REGNSKAP AS

Org. no. 821961742 Limited company (AS) Ålesund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 774,000
Equity NOK 2.8m
Incorporated 2018
Share capital NOK 100,000

JOHANSSON REGNSKAP AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 821961742. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tjenesteyting innen regnskapsføring, lønn og fakturering og hva som naturlig hører sammen med dette. Selskapet skal kunne delta i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 774,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 774,000
Equity
NOK 2.8m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns JOHANSSON REGNSKAP AS?

LOVISE HOLEN JOHANSSON
JOHANSSON REGNSKAP AS
NOK 4.2m rev. · NOK 774,000 profit

JOHANSSON REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JOHANSSON REGNSKAP AS

Who owns JOHANSSON REGNSKAP AS?

LOVISE HOLEN JOHANSSON is the largest registered owner, with 50.0%.

What is the revenue of JOHANSSON REGNSKAP AS?

JOHANSSON REGNSKAP AS had revenue of NOK 4.2m in 2024.

Who is the general manager of JOHANSSON REGNSKAP AS?

Lovise Holen Johansson is registered as general manager of JOHANSSON REGNSKAP AS.

Where is JOHANSSON REGNSKAP AS based?

JOHANSSON REGNSKAP AS has its business address in Ålesund.

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.