BIZTRAC BETA
Accounting and bookkeeping

META REGNSKAP AS

Org. no. 832353442 Limited company (AS) Råde Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 197,000
Equity NOK 147,000
Incorporated 2023
Share capital NOK 30,000

META REGNSKAP AS is registered as a limited company in Råde, Østfold with organisation number 832353442. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Regnskapsførertjenester, og økonomiske rådgivningstjenester innenfor regnskap og økonomi. Samt det som naturlig hører inn under virksomheten. Herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 197,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 197,000
Equity
NOK 147,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns META REGNSKAP AS?

TONJE TOLLEFSEN
META REGNSKAP AS
NOK 1.4m rev. · NOK 197,000 profit

META REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about META REGNSKAP AS

Who owns META REGNSKAP AS?

TONJE TOLLEFSEN is the largest registered owner, with 100.0%.

What is the revenue of META REGNSKAP AS?

META REGNSKAP AS had revenue of NOK 1.4m in 2025.

Who is the general manager of META REGNSKAP AS?

Tonje Tollefsen is registered as general manager of META REGNSKAP AS.

Where is META REGNSKAP AS based?

META REGNSKAP AS has its business address in Råde.

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.