BIZTRAC BETA
Rental and operating of own or leased real estate

CUSTOM INK AS

Org. no. 992772255 Limited company (AS) Lørenskog Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −20,000
Equity NOK 136,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−20k kr).

CUSTOM INK AS is registered as a limited company in Lørenskog, Akershus with organisation number 992772255. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av lokaler, videreformidling av tatoveringskunst, utleie av arbeidskraft, samt investeringer i eiendom og deltakelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −20,000
Equity
NOK 136,000
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns CUSTOM INK AS?

ARNE ROGER KRISTIANSEN
CUSTOM INK AS
NOK 1.1m rev. · NOK −20,000 profit

CUSTOM INK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CUSTOM INK AS

Who owns CUSTOM INK AS?

ARNE ROGER KRISTIANSEN is the largest registered owner, with 50.0%.

What is the revenue of CUSTOM INK AS?

CUSTOM INK AS had revenue of NOK 1.1m in 2024.

Who is the general manager of CUSTOM INK AS?

Tommy Ullevold is registered as general manager of CUSTOM INK AS.

Where is CUSTOM INK AS based?

CUSTOM INK AS has its business address in Kurland.

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.