BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

JENS OLAI AS

Org. no. 914165989 Limited company (AS) Hamar Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −22,000
Equity NOK 153,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

JENS OLAI AS is registered as a limited company in Hamar, Innlandet with organisation number 914165989. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 2 shares. The company's stated purpose is: “Rådgiving innen publistisk virksomhet. Medier og kommunikasjon. Analyser og dokumentasjon. Engasjement i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −22,000
Equity
NOK 153,000
Est. value
NOK 92,000

Financial health · 2025

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

Who owns JENS OLAI AS?

JENS OLAI JENSSEN
JENS OLAI AS
NOK 16,000 rev. · NOK −22,000 profit

JENS OLAI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JENS OLAI AS

Who owns JENS OLAI AS?

JENS OLAI JENSSEN is the largest registered owner, with 50.0%.

What is the revenue of JENS OLAI AS?

JENS OLAI AS had revenue of NOK 16,000 in 2025.

Who is the general manager of JENS OLAI AS?

Jens Olai Jenssen is registered as general manager of JENS OLAI AS.

Where is JENS OLAI AS based?

JENS OLAI AS has its business address in Hamar.

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.