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

MOKSNESDALEN AS

Org. no. 913853458 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 267
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).
  • Nylig endring 2026-06-30 Aksjekapital registrert 2026-06-30.

MOKSNESDALEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913853458. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▼ −131 %
Equity
NOK 267
▼ −99 %
Est. value
NOK 244

Financial health · 2025

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

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

Who owns MOKSNESDALEN AS?

MOKSNESDALEN AS
NOK 0 rev. · NOK −18,000 profit

MOKSNESDALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOKSNESDALEN AS

Who owns MOKSNESDALEN AS?

MOKSNES GÅRD AS is the largest registered owner, with 100.0%.

What is the revenue of MOKSNESDALEN AS?

MOKSNESDALEN AS had revenue of NOK 0 in 2025.

Where is MOKSNESDALEN AS based?

MOKSNESDALEN AS has its business address in Trondheim.

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.