BIZTRAC BETA
Accounting and bookkeeping

SOLVE REGNSKAPSTJENESTER AS

Org. no. 992314141 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 345,000
Equity NOK 374,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOLVE REGNSKAPSTJENESTER AS is registered as a limited company in Larvik, Vestfold with organisation number 992314141. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av regnskapstjenester og beslektede tjenester med grunnlag i føring av regnskap for andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 345,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 345,000
Equity
NOK 374,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns SOLVE REGNSKAPSTJENESTER AS?

SOLVE FORRETNINGSPARTNER AS
SOLVE REGNSKAPSTJENESTER AS
NOK 1.5m rev. · NOK 345,000 profit

SOLVE REGNSKAPSTJENESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLVE REGNSKAPSTJENESTER AS

Who owns SOLVE REGNSKAPSTJENESTER AS?

SOLVE FORRETNINGSPARTNER AS is the largest registered owner, with 100.0%.

What is the revenue of SOLVE REGNSKAPSTJENESTER AS?

SOLVE REGNSKAPSTJENESTER AS had revenue of NOK 1.5m in 2024.

Where is SOLVE REGNSKAPSTJENESTER AS based?

SOLVE REGNSKAPSTJENESTER AS has its business address in Larvik.

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.