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

REGNSKAPSPARTNER SØR AS

Org. no. 986950397 Limited company (AS) Grimstad Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 9.6m
Incorporated 2004
Share capital NOK 130,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−6k kr).

REGNSKAPSPARTNER SØR AS is registered as a limited company in Grimstad, Agder with organisation number 986950397. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2004. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Regnskapsføring, økonomisk rådgivning, andre kontorstøttetjenester, samt deltagelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −6,000
▲ +77 %
Equity
NOK 9.6m
▲ +9 %
Est. value
NOK 12.2m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
19.6%
Very good
Return on total assets
Solidity
87.9%
Very good
Equity as a share of total capital

Who owns REGNSKAPSPARTNER SØR AS?

REGNSKAPSPARTNER SØR AS
· NOK −6,000 profit

REGNSKAPSPARTNER SØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REGNSKAPSPARTNER SØR AS own?

REGNSKAPSPARTNER SØR AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about REGNSKAPSPARTNER SØR AS

Who owns REGNSKAPSPARTNER SØR AS?

Leif Inge Kristiansen is the largest registered owner, with 100.0%.

Who is the general manager of REGNSKAPSPARTNER SØR AS?

Leif Inge Kristiansen is registered as general manager of REGNSKAPSPARTNER SØR AS.

Where is REGNSKAPSPARTNER SØR AS based?

REGNSKAPSPARTNER SØR AS has its business address in Grimstad.

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.