BIZTRAC BETA
Other printing

JÆRPRINT AS

Org. no. 993286621 Limited company (AS) Klepp Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 14.3m
Operating profit NOK 172,000
Equity NOK 640,000
Incorporated 2008
Employees 9
Share capital NOK 325,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JÆRPRINT AS is registered as a limited company in Klepp, Rogaland with organisation number 993286621. The business is classified under other printing (NACE 18.120). The company was incorporated in 2008 and has 9 registered employees. Registered share capital is NOK 325,000, divided into 325000 shares. The company's stated purpose is: “Trykkerivirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.3m in revenue and NOK 172,000 in operating profit.

Key figures · 2025

Revenue
NOK 14.3m
Operating profit
NOK 172,000
Equity
NOK 640,000
Est. value
NOK 856,000

Financial health · 2025

Liquidity
1.31
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Good
Equity as a share of total capital

Who owns JÆRPRINT AS?

LUNHEIM HOLDING AS
JÆRPRINT AS
NOK 14.3m rev. · NOK 172,000 profit

JÆRPRINT AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JÆRPRINT AS

Who owns JÆRPRINT AS?

LUNHEIM HOLDING AS is the largest registered owner, with 55.0%.

What is the revenue of JÆRPRINT AS?

JÆRPRINT AS had revenue of NOK 14.3m in 2025.

Who is the general manager of JÆRPRINT AS?

Bjørn Reidar Kleppe is registered as general manager of JÆRPRINT AS.

Where is JÆRPRINT AS based?

JÆRPRINT AS has its business address in Bryne.

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.