BIZTRAC BETA
Rental and operating of own or leased real estate

WEDDES EIENDOM AS

Org. no. 928022315 Limited company (AS) Nærøysund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 372,000
Operating profit NOK 13,000
Equity NOK −1.1m
Incorporated 2021
Share capital NOK 300,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).

WEDDES EIENDOM AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 928022315. 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 300,000, divided into 300 shares. The company's stated purpose is: “Eiendomsutvikling og utleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 372,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 372,000
Operating profit
NOK 13,000
Equity
NOK −1.1m
Est. value
NOK 89,000

Financial health · 2024

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

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

Who owns WEDDES EIENDOM AS?

TRYGVE WEDDE
WEDDES EIENDOM AS
NOK 372,000 rev. · NOK 13,000 profit

WEDDES EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WEDDES EIENDOM AS

Who owns WEDDES EIENDOM AS?

TRYGVE WEDDE is the largest registered owner, with 50.0%.

What is the revenue of WEDDES EIENDOM AS?

WEDDES EIENDOM AS had revenue of NOK 372,000 in 2024.

Who is the general manager of WEDDES EIENDOM AS?

Trygve Wedde is registered as general manager of WEDDES EIENDOM AS.

Where is WEDDES EIENDOM AS based?

WEDDES EIENDOM AS has its business address in Kolvereid.

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.