BIZTRAC BETA
COMPANY REGISTER PROFILE
997168534 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

COPARTNER AS

Org. no. 997168534 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 113,000
Operating profit NOK −4,000
Equity NOK 101,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

COPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 997168534. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Levere konsulenttimer. Selskapet kan eie og investere i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 113,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 113,000
Operating profit
NOK −4,000
Equity
NOK 101,000
Est. value
NOK 168,000

Financial health · 2025

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

Who owns COPARTNER AS?

HANNE FOSSE
COPARTNER AS
NOK 113,000 rev. · NOK −4,000 profit

COPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COPARTNER AS

Who owns COPARTNER AS?

HANNE FOSSE is the largest registered owner, with 100.0%.

What is the revenue of COPARTNER AS?

COPARTNER AS had revenue of NOK 113,000 in 2025.

Who is the general manager of COPARTNER AS?

Hanne Fosse is registered as general manager of COPARTNER AS.

Where is COPARTNER AS based?

COPARTNER AS has its business address in Oslo.

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.