biztrac. BETA
COMPANY REGISTER PROFILE
932692678 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

KIRKEGATA 43 EIENDOM AS

Org. no. 932692678 Limited company (AS) Steinkjer Incorporated 2023 Active
Operating profit NOK −53,000
Equity NOK 36,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KIRKEGATA 43 EIENDOM AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 932692678. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av eiendommer, eiendomsutvikling og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −53,000
▼ −93 %
Equity
NOK 36,000
▲ +395 %
Est. value
NOK 32,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
0.5%
Weak
Equity as a share of total capital

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

Who owns KIRKEGATA 43 EIENDOM AS?

KIRKEGATA 43 EIENDOM AS
· NOK −53,000 profit

KIRKEGATA 43 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KIRKEGATA 43 EIENDOM AS er morselskap for 3 datterselskaper:

Frequently asked questions about KIRKEGATA 43 EIENDOM AS

Who owns KIRKEGATA 43 EIENDOM AS?

FUGLESANGDAHL AS is the largest registered owner, with 100.0%.

Where is KIRKEGATA 43 EIENDOM AS based?

KIRKEGATA 43 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.