BIZTRAC BETA
COMPANY REGISTER PROFILE
997031946 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

COG EIENDOM AS

Org. no. 997031946 Limited company (AS) Stange Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 61,000
Operating profit NOK −93,000
Equity NOK 890,000
Incorporated 2011
Share capital NOK 150,000

Signals

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

COG EIENDOM AS is registered as a limited company in Stange, Innlandet with organisation number 997031946. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Kjøp og salg av eiendom, utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 61,000 in revenue and NOK −93,000 in operating profit.

Key figures · 2025

Revenue
NOK 61,000
▼ −94 %
Operating profit
NOK −93,000
▼ −109 %
Equity
NOK 890,000
▼ −8 %
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns COG EIENDOM AS?

COG EIENDOM AS
NOK 61,000 rev. · NOK −93,000 profit

COG EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about COG EIENDOM AS

Who owns COG EIENDOM AS?

ERLAND NORDBY is the largest registered owner, with 33.3%.

What is the revenue of COG EIENDOM AS?

COG EIENDOM AS had revenue of NOK 61,000 in 2025.

Who is the general manager of COG EIENDOM AS?

Anders Haug is registered as general manager of COG EIENDOM AS.

Where is COG EIENDOM AS based?

COG EIENDOM AS has its business address in Espa.

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.