BIZTRAC BETA
Accounting and bookkeeping

TOPNOR REGNSKAP AS

Org. no. 930094757 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK 255,000
Equity NOK 259,000
Incorporated 2022
Employees 6
Share capital NOK 30,000

TOPNOR REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 930094757. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2022 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Regnskapsførsel for andre selskaper,årsoppgjør og ligningspapirer, økonomisk rådgivning, samt andre produkter/tjenester som naturlig hører sammen med dette. I tillegg kan selskapet engasjere seg økonomisk i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK 255,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK 255,000
Equity
NOK 259,000
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns TOPNOR REGNSKAP AS?

TOPNOR AS
TOPNOR REGNSKAP AS
NOK 4.1m rev. · NOK 255,000 profit

TOPNOR REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPNOR REGNSKAP AS

Who owns TOPNOR REGNSKAP AS?

TOPNOR AS is the largest registered owner, with 50.0%.

What is the revenue of TOPNOR REGNSKAP AS?

TOPNOR REGNSKAP AS had revenue of NOK 4.1m in 2024.

Who is the general manager of TOPNOR REGNSKAP AS?

Angelika Magdalena Wcislo is registered as general manager of TOPNOR REGNSKAP AS.

Where is TOPNOR REGNSKAP AS based?

TOPNOR REGNSKAP AS has its business address in Oslo.

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.