biztrac. BETA
COMPANY REGISTER PROFILE
914458161 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HALLINGSKARVET 2025 AS

Org. no. 914458161 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK 602,000
Incorporated 2014
Share capital NOK 630,000

Signals

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

HALLINGSKARVET 2025 AS is registered as a limited company in Oslo, Oslo with organisation number 914458161. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 630,000, divided into 630 shares. The company's stated purpose is: “Investering, utvikling og drift av eiendom av enhver art og alt som er forbundet med slik virksomhet.”.

Former names: CMG - COURSEMADEGOOD AS

Key figures · 2025

Operating profit
NOK −35,000
▲ +45 %
Equity
NOK 602,000
▲ +1521 %
Est. value
NOK 550,000

Financial health · 2025

Liquidity
84.34
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
4.3%
Weak
Equity as a share of total capital

Who owns HALLINGSKARVET 2025 AS?

HALLINGSKARVET 2025 AS
· NOK −35,000 profit

HALLINGSKARVET 2025 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HALLINGSKARVET 2025 AS own?

HALLINGSKARVET 2025 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HALLINGSKARVET 2025 AS

Who owns HALLINGSKARVET 2025 AS?

GADE AS is the largest registered owner, with 50.0%.

Who is the general manager of HALLINGSKARVET 2025 AS?

Morten Henrik Greidung is registered as general manager of HALLINGSKARVET 2025 AS.

Where is HALLINGSKARVET 2025 AS based?

HALLINGSKARVET 2025 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 03.10.2026.

Report a problem

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