BIZTRAC BETA
Rental and operating of own or leased real estate

DYNAMITTVEIEN 11 AS

Org. no. 927205343 Limited company (AS) Bamble Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.6m
Equity NOK 3.1m
Incorporated 2021
Share capital NOK 215,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-07 Adresseendring registrert 2026-04-07.

DYNAMITTVEIEN 11 AS is registered as a limited company in Bamble, Telemark with organisation number 927205343. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 215,000, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.6m
Equity
NOK 3.1m
Est. value
NOK 5.4m

Financial health · 2024

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.8%
Very good
Equity as a share of total capital

Who owns DYNAMITTVEIEN 11 AS?

ITERATIV EIENDOM AS
DYNAMITTVEIEN 11 AS
NOK 2.2m rev. · NOK 1.6m profit

DYNAMITTVEIEN 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DYNAMITTVEIEN 11 AS

Who owns DYNAMITTVEIEN 11 AS?

ITERATIV EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of DYNAMITTVEIEN 11 AS?

DYNAMITTVEIEN 11 AS had revenue of NOK 2.2m in 2024.

Where is DYNAMITTVEIEN 11 AS based?

DYNAMITTVEIEN 11 AS has its business address in Stathelle.

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.