BIZTRAC BETA
Construction of residential and non-residential buildings

SERVICE 7024 AS

Org. no. 925322725 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 660
Operating profit NOK −76,000
Equity NOK −83,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−83k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−76k kr).

SERVICE 7024 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925322725. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Transport, service og vedlikehold av maskiner og andre tjenester, teknisk konsulentvirksomhet og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 660 in revenue and NOK −76,000 in operating profit.

Key figures · 2025

Revenue
NOK 660
Operating profit
NOK −76,000
Equity
NOK −83,000

Financial health · 2025

Liquidity
2.03
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-246.6%
Weak
Equity as a share of total capital

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

Who owns SERVICE 7024 AS?

Martin Rosvold
SERVICE 7024 AS
NOK 660 rev. · NOK −76,000 profit

SERVICE 7024 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SERVICE 7024 AS

Who owns SERVICE 7024 AS?

Martin Rosvold is the largest registered owner, with 100.0%.

What is the revenue of SERVICE 7024 AS?

SERVICE 7024 AS had revenue of NOK 660 in 2025.

Where is SERVICE 7024 AS based?

SERVICE 7024 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 15.06.2026.

Report a problem

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