BIZTRAC BETA
Other captive investment companies

PAULIN HOLDING AS

Org. no. 921341997 Limited company (AS) Nittedal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 498,000
Incorporated 2018
Share capital NOK 35,000

Signals

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

PAULIN HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 921341997. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 35,000, divided into 350 shares. The company's stated purpose is: “Investering og deltagelse i andre selskaper, kjøp og salg av aksjer, samt andre investeringer og oppgaver som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 498,000
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns PAULIN HOLDING AS?

FRANCIS DOUGHERTY PAULIN
PAULIN HOLDING AS
NOK 0 rev. · NOK −12,000 profit

PAULIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PAULIN HOLDING AS own?

PAULIN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PAULIN HOLDING AS

Who owns PAULIN HOLDING AS?

FRANCIS DOUGHERTY PAULIN is the largest registered owner, with 100.0%.

What is the revenue of PAULIN HOLDING AS?

PAULIN HOLDING AS had revenue of NOK 0 in 2025.

Where is PAULIN HOLDING AS based?

PAULIN HOLDING AS has its business address in Nittedal.

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.