biztrac. BETA
COMPANY REGISTER PROFILE
994913514 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Technical testing and analysis

SOFT SERTIFISERING AS

Org. no. 994913514 Limited company (AS) Bergen Incorporated 2010 Active
Revenue 2025 NOK 8.9m
Operating profit NOK 1.6m
Equity NOK 13.6m
Incorporated 2010
Employees 31
Share capital NOK 100,000

SOFT SERTIFISERING AS is registered as a limited company in Bergen, Vestland with organisation number 994913514. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2010 and has 31 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tilby tjenester for sertifisering av personell og bedrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
▼ −4 %
Operating profit
NOK 1.6m
▼ −34 %
Equity
NOK 13.6m
▲ +14 %
Est. value
NOK 16.8m

Financial health · 2025

Liquidity
5.87
Very good
Current assets ÷ current liabilities
Profitability
14.1%
Good
Return on total assets
Solidity
85.6%
Very good
Equity as a share of total capital

Who owns SOFT SERTIFISERING AS?

SOFT SERTIFISERING AS
NOK 8.9m rev. · NOK 1.6m profit

SOFT SERTIFISERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOFT SERTIFISERING AS

Who owns SOFT SERTIFISERING AS?

SAMARBEIDSORGANET FOR TILKOMSTTEKNIKK is the largest registered owner, with 100.0%.

What is the revenue of SOFT SERTIFISERING AS?

SOFT SERTIFISERING AS had revenue of NOK 8.9m in 2025.

Who is the general manager of SOFT SERTIFISERING AS?

Bjarte Sollesnes is registered as general manager of SOFT SERTIFISERING AS.

Where is SOFT SERTIFISERING AS based?

SOFT SERTIFISERING 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.