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

KRIMA EIENDOM AS

Org. no. 929006119 Limited company (AS) Namsos Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 93,000
Operating profit NOK 43,000
Equity NOK 365,000
Incorporated 2022
Share capital NOK 800,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KRIMA EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 929006119. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 800,000, divided into 8000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom, samt hva naturlig hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 93,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 93,000
▲ +40 %
Operating profit
NOK 43,000
▲ +173 %
Equity
NOK 365,000
▼ −58 %
Est. value
NOK 392,000

Financial health · 2025

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

Who owns KRIMA EIENDOM AS?

KRIMA EIENDOM AS
NOK 93,000 rev. · NOK 43,000 profit

KRIMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRIMA EIENDOM AS

Who owns KRIMA EIENDOM AS?

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

What is the revenue of KRIMA EIENDOM AS?

KRIMA EIENDOM AS had revenue of NOK 93,000 in 2025.

Where is KRIMA EIENDOM AS based?

KRIMA EIENDOM AS has its business address in Bangsund.

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.