BIZTRAC BETA
Industrial product and fashion design activities

MURLONG CRES AS

Org. no. 932412225 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK 654,000
Equity NOK −197,000
Incorporated 2023
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−197k kr).

MURLONG CRES AS is registered as a limited company in Drammen, Buskerud with organisation number 932412225. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2023 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Designer og syr klær og digitale symønstre.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 654,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
Operating profit
NOK 654,000
Equity
NOK −197,000
Est. value
NOK 4.4m

Financial health · 2025

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

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

Who owns MURLONG CRES AS?

KAJA HØGLUND
MURLONG CRES AS
NOK 8.4m rev. · NOK 654,000 profit

MURLONG CRES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MURLONG CRES AS

Who owns MURLONG CRES AS?

KAJA HØGLUND is the largest registered owner, with 100.0%.

What is the revenue of MURLONG CRES AS?

MURLONG CRES AS had revenue of NOK 8.4m in 2025.

Who is the general manager of MURLONG CRES AS?

Kaja Høglund is registered as general manager of MURLONG CRES AS.

Where is MURLONG CRES AS based?

MURLONG CRES AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.