BIZTRAC BETA
Accounting and bookkeeping

INGRIDS REGNSKAPSKONTOR AS

Org. no. 975824098 Limited company (AS) Ålesund Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 816,000
Operating profit NOK 8,000
Equity NOK 319,000
Incorporated 1995
Share capital NOK 100,000

INGRIDS REGNSKAPSKONTOR AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 975824098. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Konsulent-tjenester, regnskap/økonomi, og hva hermed står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 816,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 816,000
Operating profit
NOK 8,000
Equity
NOK 319,000
Est. value
NOK 212,000

Financial health · 2024

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

Who owns INGRIDS REGNSKAPSKONTOR AS?

INGRID BAKKENE
INGRIDS REGNSKAPSKONTOR AS
NOK 816,000 rev. · NOK 8,000 profit

INGRIDS REGNSKAPSKONTOR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INGRIDS REGNSKAPSKONTOR AS

Who owns INGRIDS REGNSKAPSKONTOR AS?

INGRID BAKKENE is the largest registered owner, with 98.0%.

What is the revenue of INGRIDS REGNSKAPSKONTOR AS?

INGRIDS REGNSKAPSKONTOR AS had revenue of NOK 816,000 in 2024.

Who is the general manager of INGRIDS REGNSKAPSKONTOR AS?

Ingrid Bakkene is registered as general manager of INGRIDS REGNSKAPSKONTOR AS.

Where is INGRIDS REGNSKAPSKONTOR AS based?

INGRIDS REGNSKAPSKONTOR AS has its business address in Ellingsøy.

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.