BIZTRAC BETA
Development of building projects

TVEDESTRAND BOLIGUTVIKLING AS

Org. no. 932199165 Limited company (AS) Tvedestrand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 932,000
Operating profit NOK 746,000
Equity NOK 499,000
Incorporated 2023
Share capital NOK 30,000

TVEDESTRAND BOLIGUTVIKLING AS is registered as a limited company in Tvedestrand, Agder with organisation number 932199165. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av egen fast eiendom ellers.”. The most recent filed accounts, for the 2024 financial year, show NOK 932,000 in revenue and NOK 746,000 in operating profit.

Key figures · 2024

Revenue
NOK 932,000
Operating profit
NOK 746,000
Equity
NOK 499,000
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
2.18
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.6%
Good
Equity as a share of total capital

Who owns TVEDESTRAND BOLIGUTVIKLING AS?

VISJON INVEST AS
TVEDESTRAND BOLIGUTVIKLING AS
NOK 932,000 rev. · NOK 746,000 profit

TVEDESTRAND BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TVEDESTRAND BOLIGUTVIKLING AS

Who owns TVEDESTRAND BOLIGUTVIKLING AS?

VISJON INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of TVEDESTRAND BOLIGUTVIKLING AS?

TVEDESTRAND BOLIGUTVIKLING AS had revenue of NOK 932,000 in 2024.

Who is the general manager of TVEDESTRAND BOLIGUTVIKLING AS?

Marcus Bjerkeseth Marcussen is registered as general manager of TVEDESTRAND BOLIGUTVIKLING AS.

Where is TVEDESTRAND BOLIGUTVIKLING AS based?

TVEDESTRAND BOLIGUTVIKLING AS has its business address in Tvedestrand.

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.