biztrac. BETA
COMPANY REGISTER PROFILE
968154826 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other software publishing

CREDITVIEW AS

Org. no. 968154826 Limited company (AS) Bergen Incorporated 1993 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK −3.1m
Incorporated 1993
Share capital NOK 1.4m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

CREDITVIEW AS is registered as a limited company in Bergen, Vestland with organisation number 968154826. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 1993. Registered share capital is NOK 1.4m, divided into 1375000 shares. The company's stated purpose is: “Selge, utvikle og forvalte programvareproduktet CreditView og andre programvareprodukter, med til- hørende vedlikeholds- og konsulenttjenester for det internasjonale og norske markedet, samt del- tagelse i andre selskaper med lignende virksomhet.”.

Former names: LOGICA AS, EYECON AS

Key figures · 2025

Operating profit
NOK −19,000
▼ −86 %
Equity
NOK −3.1m
▼ −1 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-1574824.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns CREDITVIEW AS?

PLENTEOUS CORP., ADR. SVEITS CH
CREDITVIEW AS
· NOK −19,000 profit

CREDITVIEW AS has 1 registered shareholder:

  • PLENTEOUS CORP., ADR. SVEITS 100.0%
All shareholders and roles →

Frequently asked questions about CREDITVIEW AS

Who owns CREDITVIEW AS?

PLENTEOUS CORP., ADR. SVEITS is the largest registered owner, with 100.0%.

Where is CREDITVIEW AS based?

CREDITVIEW AS has its business address in Bergen.

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.