BIZTRAC BETA
Accounting and bookkeeping

JAMA REGNSKAPSSERVICE AS

Org. no. 950721820 Limited company (AS) Nærøysund Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 237,000
Equity NOK 576,000
Incorporated 1988
Share capital NOK 190,000

Signals

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

JAMA REGNSKAPSSERVICE AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 950721820. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1988. Registered share capital is NOK 190,000, divided into 758 shares. The company's stated purpose is: “Å drive regnskapsservice samt annen virksomhet som kan styrke virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 237,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 237,000
Equity
NOK 576,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns JAMA REGNSKAPSSERVICE AS?

VIPLAST AS
JAMA REGNSKAPSSERVICE AS
NOK 4.3m rev. · NOK 237,000 profit

JAMA REGNSKAPSSERVICE AS has 20+ registered shareholders:

All shareholders and roles →

Group structure

JAMA REGNSKAPSSERVICE AS er morselskap for 1 datterselskap:

Frequently asked questions about JAMA REGNSKAPSSERVICE AS

Who owns JAMA REGNSKAPSSERVICE AS?

VIPLAST AS is the largest registered owner, with 55.9%.

What is the revenue of JAMA REGNSKAPSSERVICE AS?

JAMA REGNSKAPSSERVICE AS had revenue of NOK 4.3m in 2024.

Where is JAMA REGNSKAPSSERVICE AS based?

JAMA REGNSKAPSSERVICE AS has its business address in Austafjord.

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.