BIZTRAC BETA
Rental and operating of own or leased real estate

GROSVOLDVEIEN 144 AS

Org. no. 925938416 Limited company (AS) Kongsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 1.0m
Equity NOK 733,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

GROSVOLDVEIEN 144 AS is registered as a limited company in Kongsberg, Buskerud with organisation number 925938416. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsbesittelse med utleie og annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 1.0m
Equity
NOK 733,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns GROSVOLDVEIEN 144 AS?

MIKALSEN HOLDINGSELSKAP AS
GROSVOLDVEIEN 144 AS
NOK 1.7m rev. · NOK 1.0m profit

GROSVOLDVEIEN 144 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GROSVOLDVEIEN 144 AS er morselskap for 2 datterselskaper:

Frequently asked questions about GROSVOLDVEIEN 144 AS

Who owns GROSVOLDVEIEN 144 AS?

MIKALSEN HOLDINGSELSKAP AS is the largest registered owner, with 100.0%.

What is the revenue of GROSVOLDVEIEN 144 AS?

GROSVOLDVEIEN 144 AS had revenue of NOK 1.7m in 2024.

Where is GROSVOLDVEIEN 144 AS based?

GROSVOLDVEIEN 144 AS has its business address in Skollenborg.

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.