BIZTRAC BETA
COMPANY REGISTER PROFILE
835375722 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KRM HOLDING AS

Org. no. 835375722 Limited company (AS) Verdal Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −5
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

KRM HOLDING AS is registered as a limited company in Verdal, Trøndelag with organisation number 835375722. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og eiendeler.”.

Key figures · 2025

Operating profit
NOK −5
Equity
NOK 23,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns KRM HOLDING AS?

KRM HOLDING AS
· NOK −5 profit

KRM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRM HOLDING AS own?

KRM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRM HOLDING AS

Who owns KRM HOLDING AS?

KIM ROBERT MYRVOLD is the largest registered owner, with 100.0%.

Where is KRM HOLDING AS based?

KRM HOLDING AS has its business address in Verdal.

Property

Business address Volhaugvegen 187, 7655 Verdal
Cadastral unit 5038-19/908/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.