BIZTRAC BETA
Computer programming activities

TRIGRAM AS

Org. no. 916222440 Limited company (AS) Stavanger Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −59,000
Equity NOK 64,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

TRIGRAM AS is registered as a limited company in Stavanger, Rogaland with organisation number 916222440. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Programvareutvikling på oppdrag for kunde, utvikling av egen programvare for salg, deltakelse i tilsvarende selskap, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −59,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −59,000
Equity
NOK 64,000
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Weak
Equity as a share of total capital

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

Who owns TRIGRAM AS?

KEVIN BRUBECK UNHAMMER
TRIGRAM AS
NOK 1.8m rev. · NOK −59,000 profit

TRIGRAM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIGRAM AS

Who owns TRIGRAM AS?

KEVIN BRUBECK UNHAMMER is the largest registered owner, with 44.0%.

What is the revenue of TRIGRAM AS?

TRIGRAM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of TRIGRAM AS?

Kevin Brubeck Unhammer is registered as general manager of TRIGRAM AS.

Where is TRIGRAM AS based?

TRIGRAM AS has its business address in Stavanger.

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.