BIZTRAC BETA
COMPANY REGISTER PROFILE
919572949 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

KRISMA AS

Org. no. 919572949 Limited company (AS) Ringsaker Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −90,000
Equity NOK 4.1m
Incorporated 2017
Share capital NOK 30,000

Signals

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

KRISMA AS is registered as a limited company in Ringsaker, Innlandet with organisation number 919572949. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og andre selskaper, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −90,000
Equity
NOK 4.1m
Est. value
NOK 9.2m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.5%
Very good
Equity as a share of total capital

Who owns KRISMA AS?

KRISMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KRISMA AS

Who owns KRISMA AS?

TOM ERIK LEHNE is the largest registered owner, with 86.7%.

Where is KRISMA AS based?

KRISMA AS has its business address in Brumunddal.

Property

Business address c/o Tom Erik Lehne Leilighet H1201 Tårnvegen 55, 2380 Brumunddal
Cadastral unit 3411-1/384/0/0
Building Annen kontorbygning · 33 units

10 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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