BIZTRAC BETA
Accounting and bookkeeping

BAKKEN REGNSKAP AS

Org. no. 920250858 Limited company (AS) Midtre Gauldal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −43,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−43k kr).

BAKKEN REGNSKAP AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 920250858. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Regnskap, økonomisk rådgivning, kurs, investering i andre selskap og tilhørende virksomhet, kjøp og salg av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −43,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-75957.1%
Weak
Equity as a share of total capital

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

Who owns BAKKEN REGNSKAP AS?

Steinar Endal Bakken
BAKKEN REGNSKAP AS
NOK 0 rev. · NOK 0 profit

BAKKEN REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAKKEN REGNSKAP AS

Who owns BAKKEN REGNSKAP AS?

Steinar Endal Bakken is the largest registered owner, with 100.0%.

What is the revenue of BAKKEN REGNSKAP AS?

BAKKEN REGNSKAP AS had revenue of NOK 0 in 2024.

Who is the general manager of BAKKEN REGNSKAP AS?

Steinar Endal Bakken is registered as general manager of BAKKEN REGNSKAP AS.

Where is BAKKEN REGNSKAP AS based?

BAKKEN REGNSKAP AS has its business address in Støren.

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.