biztrac. BETA
COMPANY REGISTER PROFILE
914397111 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

VERIFIED AS

Org. no. 914397111 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 33.4m
Operating profit NOK −162,000
Equity NOK 3.0m
Incorporated 2014
Employees 9
Share capital NOK 38,000

Signals

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

VERIFIED AS is registered as a limited company in Oslo, Oslo with organisation number 914397111. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014 and has 9 registered employees. Registered share capital is NOK 38,000, divided into 3750 shares. The company's stated purpose is: “Tilby løsninger for elektronisk signering av dokumenter, samt virksomhet som hermed står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.4m in revenue and NOK −162,000 in operating profit.

Key figures · 2025

Revenue
NOK 33.4m
▲ +29 %
Operating profit
NOK −162,000
▲ +98 %
Equity
NOK 3.0m
▲ +261 %
Est. value
NOK 56.3m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
-0.8%
Not satisfactory
Return on total assets
Solidity
17.5%
Satisfactory
Equity as a share of total capital

Who owns VERIFIED AS?

VERIFIED GLOBAL AB SE
VERIFIED AS
NOK 33.4m rev. · NOK −162,000 profit

VERIFIED AS has 1 registered shareholder:

  • VERIFIED GLOBAL AB 100.0%
All shareholders and roles →

Frequently asked questions about VERIFIED AS

Who owns VERIFIED AS?

VERIFIED GLOBAL AB is the largest registered owner, with 100.0%.

What is the revenue of VERIFIED AS?

VERIFIED AS had revenue of NOK 33.4m in 2025.

Where is VERIFIED AS based?

VERIFIED AS has its business address in Oslo.

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.