biztrac. BETA
COMPANY REGISTER PROFILE
930068071 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

SHIFT REGNSKAP AS

Org. no. 930068071 Limited company (AS) Farsund Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 408,000
Equity NOK 665,000
Incorporated 2022
Share capital NOK 30,000

SHIFT REGNSKAP AS is registered as a limited company in Farsund, Agder with organisation number 930068071. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Leveranse av økonomitjenester innenfor regnskap, lønn og rådgivning, konsulenttjenester, undervisning, samt investering i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 408,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▲ +23 %
Operating profit
NOK 408,000
▲ +33 %
Equity
NOK 665,000
▲ +91 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
2.58
Very good
Current assets ÷ current liabilities
Profitability
45.7%
Very good
Return on total assets
Solidity
61.2%
Very good
Equity as a share of total capital

Who owns SHIFT REGNSKAP AS?

SHIFT REGNSKAP AS
NOK 2.0m rev. · NOK 408,000 profit

SHIFT REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHIFT REGNSKAP AS

Who owns SHIFT REGNSKAP AS?

Birgit Johansen is the largest registered owner, with 100.0%.

What is the revenue of SHIFT REGNSKAP AS?

SHIFT REGNSKAP AS had revenue of NOK 2.0m in 2025.

Who is the general manager of SHIFT REGNSKAP AS?

Birgit Johansen is registered as general manager of SHIFT REGNSKAP AS.

Where is SHIFT REGNSKAP AS based?

SHIFT REGNSKAP AS has its business address in Vanse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.