biztrac. BETA
COMPANY REGISTER PROFILE
989789635 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

RÅD & REGNSKAP HOLDING AS

Org. no. 989789635 Limited company (AS) Kinn Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 597,000
Incorporated 2006
Share capital NOK 600,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-10-01 Adresseendring registrert 2026-10-01.

RÅD & REGNSKAP HOLDING AS is registered as a limited company in Kinn, Vestland with organisation number 989789635. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2006. Registered share capital is NOK 600,000, divided into 60 shares. The company's stated purpose is: “Investering i selskaper som driver med regnskapstjenester og rådgivning, herunder virksomhet som står i den forbindelse. Selskapet kan også delta i andre selskaper med beslektet formål.”.

Key figures · 2025

Operating profit
NOK −7,000
▼ −294 %
Equity
NOK 597,000
▼ −1 %
Est. value
NOK 970,000

Financial health · 2025

Liquidity
2227.64
Very good
Current assets ÷ current liabilities
Profitability
-0.8%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns RÅD & REGNSKAP HOLDING AS?

RÅD & REGNSKAP HOLDING AS
· NOK −7,000 profit

RÅD & REGNSKAP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RÅD & REGNSKAP HOLDING AS

Who owns RÅD & REGNSKAP HOLDING AS?

T HAVN AS is the largest registered owner, with 100.0%.

Where is RÅD & REGNSKAP HOLDING AS based?

RÅD & REGNSKAP HOLDING AS has its business address in Florø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.