BIZTRAC BETA
Computer programming activities

IPSUM AS

Org. no. 914228794 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK −140,000
Equity NOK −29,000
Incorporated 2014
Employees 5
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−29k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−140k kr).

IPSUM AS is registered as a limited company in Bergen, Vestland with organisation number 914228794. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikle og selge skreddersydde IT-løsninger primært innen kvalitet & HMS, enten direkte eller indirekte gjennom eierskap i andre selskaper. Selskapet skal også kunne drive rådgivning/konsulentvirksomhet innen samme fagfelt.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK −140,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK −140,000
Equity
NOK −29,000

Financial health · 2024

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.4%
Weak
Equity as a share of total capital

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

Who owns IPSUM AS?

Ole Bård Berg
IPSUM AS
NOK 3.9m rev. · NOK −140,000 profit

IPSUM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about IPSUM AS

Who owns IPSUM AS?

Ole Bård Berg is the largest registered owner, with 50.0%.

What is the revenue of IPSUM AS?

IPSUM AS had revenue of NOK 3.9m in 2025.

Where is IPSUM AS based?

IPSUM AS has its business address in Loddefjord.

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

Report a problem

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