biztrac. BETA
COMPANY REGISTER PROFILE
916231849 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KG28 EIENDOM AS

Org. no. 916231849 Limited company (AS) Steinkjer Incorporated 1939 Active
Revenue 2025 NOK 2.4m
Operating profit NOK −65,000
Equity NOK 47,000
Incorporated 1939
Share capital NOK 120,000

Signals

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

KG28 EIENDOM AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 916231849. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1939. Registered share capital is NOK 120,000. The company's stated purpose is: “Erverv av, utbygging og drift av fast eiendom samt virksomhet som har forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −65,000 in operating profit.

Former names: HOUGEN EIENDOM AS, SEVEREIDE EIENDOM AS

Key figures · 2025

Revenue
NOK 2.4m
▲ +5 %
Operating profit
NOK −65,000
▲ +93 %
Equity
NOK 47,000
▼ −86 %
Est. value
NOK 3.6m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KG28 EIENDOM AS?

KG28 EIENDOM AS
NOK 2.4m rev. · NOK −65,000 profit

KG28 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KG28 EIENDOM AS

Who owns KG28 EIENDOM AS?

PLG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KG28 EIENDOM AS?

KG28 EIENDOM AS had revenue of NOK 2.4m in 2025.

Where is KG28 EIENDOM AS based?

KG28 EIENDOM AS has its business address in Steinkjer.

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.