BIZTRAC BETA
COMPANY REGISTER PROFILE
935546230 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KLØVER 2 AS

Org. no. 935546230 Limited company (AS) Tromsø Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 6.9m
Incorporated 2025
Share capital NOK 209,000

Signals

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

KLØVER 2 AS is registered as a limited company in Tromsø, Troms with organisation number 935546230. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 209,000, divided into 117 shares. The company's stated purpose is: “Eie av aksje og andeler i andre selskaper samt andre kapitalplasseringer.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 6.9m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns KLØVER 2 AS?

KLØVER 2 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KLØVER 2 AS own?

KLØVER 2 AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KLØVER 2 AS

Who owns KLØVER 2 AS?

KLØVEREIE AS is the largest registered owner, with 55.9%.

Where is KLØVER 2 AS based?

KLØVER 2 AS has its business address in Tromsø.

Property

Business address Winston Churchills veg 75, 9014 Tromsø
Cadastral unit 5501-117/355/0/0
Building Rekkehus · 4 units

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.