BIZTRAC BETA
Accounting and bookkeeping

RE REGNSKAP AS

Org. no. 976130987 Limited company (AS) Tønsberg Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK −579,000
Equity NOK 844,000
Incorporated 1996
Employees 5
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−579k kr).

RE REGNSKAP AS is registered as a limited company in Tønsberg, Vestfold with organisation number 976130987. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1996 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Regnskapsføring, forsikrings-/plasserings- formidling, økonomisk veiledning og andre områder som har nær tilknytning til det ovenstående.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK −579,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK −579,000
Equity
NOK 844,000
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns RE REGNSKAP AS?

TOR ARNE VITTERSØ
RE REGNSKAP AS
NOK 4.7m rev. · NOK −579,000 profit

RE REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RE REGNSKAP AS

Who owns RE REGNSKAP AS?

TOR ARNE VITTERSØ is the largest registered owner, with 100.0%.

What is the revenue of RE REGNSKAP AS?

RE REGNSKAP AS had revenue of NOK 4.7m in 2024.

Who is the general manager of RE REGNSKAP AS?

Tor Arne Vittersø is registered as general manager of RE REGNSKAP AS.

Where is RE REGNSKAP AS based?

RE REGNSKAP AS has its business address in Ramnes.

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.