BIZTRAC BETA
Accounting and bookkeeping

BJØRKAN REGNSKAP AS

Org. no. 976089790 Limited company (AS) Midtre Gauldal Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 12.7m
Operating profit NOK 420,000
Equity NOK 4.1m
Incorporated 1996
Employees 15
Share capital NOK 100,000

BJØRKAN REGNSKAP AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 976089790. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1996 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Regnskapskontor og hva dermed står i forbindelse, dessuten ved aksjeeie eller på annen måte gjøre seg interessert i annen forretningsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.7m in revenue and NOK 420,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.7m
Operating profit
NOK 420,000
Equity
NOK 4.1m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns BJØRKAN REGNSKAP AS?

ELIN BJØRKAN VIK
BJØRKAN REGNSKAP AS
NOK 12.7m rev. · NOK 420,000 profit

BJØRKAN REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRKAN REGNSKAP AS

Who owns BJØRKAN REGNSKAP AS?

ELIN BJØRKAN VIK is the largest registered owner, with 50.0%.

What is the revenue of BJØRKAN REGNSKAP AS?

BJØRKAN REGNSKAP AS had revenue of NOK 12.7m in 2024.

Who is the general manager of BJØRKAN REGNSKAP AS?

Kjersti Marie Røttum is registered as general manager of BJØRKAN REGNSKAP AS.

Where is BJØRKAN REGNSKAP AS based?

BJØRKAN REGNSKAP AS has its business address in Budalen.

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.