BIZTRAC BETA
Rental and operating of own or leased real estate

ERIK WEDUM AS

Org. no. 918953248 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1,000,000
Operating profit NOK 447,000
Equity NOK 2.2m
Incorporated 2017
Share capital NOK 100,000

ERIK WEDUM AS is registered as a limited company in Lillehammer, Innlandet with organisation number 918953248. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg, samt utleie av fast eiendom og andre produkter/tjenester som naturlig hører til dette. Herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000,000 in revenue and NOK 447,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000,000
Operating profit
NOK 447,000
Equity
NOK 2.2m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns ERIK WEDUM AS?

ERIK WEDUM
ERIK WEDUM AS
NOK 1,000,000 rev. · NOK 447,000 profit

ERIK WEDUM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERIK WEDUM AS

Who owns ERIK WEDUM AS?

ERIK WEDUM is the largest registered owner, with 100.0%.

What is the revenue of ERIK WEDUM AS?

ERIK WEDUM AS had revenue of NOK 1,000,000 in 2025.

Who is the general manager of ERIK WEDUM AS?

Erik Wedum is registered as general manager of ERIK WEDUM AS.

Where is ERIK WEDUM AS based?

ERIK WEDUM AS has its business address in Fåberg.

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.