BIZTRAC BETA
Rental and operating of own or leased real estate

TIP HOLDING AS

Org. no. 917203849 Limited company (AS) Tana Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 3.4m
Equity NOK 139.6m
Incorporated 2016
Share capital NOK 5.0m

Signals

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

TIP HOLDING AS is registered as a limited company in Tana, Finnmark with organisation number 917203849. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 5.0m, divided into 500 shares. The company's stated purpose is: “Å eie aksjer eller andeler i andre selskap, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 3.4m
Equity
NOK 139.6m
Est. value
NOK 104.7m

Financial health · 2024

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

Who owns TIP HOLDING AS?

TROND IVAR PEDERSEN
TIP HOLDING AS
NOK 4.3m rev. · NOK 3.4m profit

TIP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TIP HOLDING AS own?

TIP HOLDING AS holds stakes in 21 companies:

See the full ownership structure →

Frequently asked questions about TIP HOLDING AS

Who owns TIP HOLDING AS?

TROND IVAR PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TIP HOLDING AS?

TIP HOLDING AS had revenue of NOK 4.3m in 2024.

Where is TIP HOLDING AS based?

TIP HOLDING AS has its business address in Tana.

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.