BIZTRAC BETA
Other real estate activities on a fee or contract basis

WELLE ENTREPRENØR AS

Org. no. 918632379 Limited company (AS) Øyer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK −226,000
Equity NOK 701,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−226k kr).

WELLE ENTREPRENØR AS is registered as a limited company in Øyer, Innlandet with organisation number 918632379. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forestå effektiv og god forvaltning av eiendommer og alt hva herved står i forbindelse, samt deltagelse i annen forretningsvirksomhet, herunder utleie og drift av eiendom og alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK −226,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK −226,000
Equity
NOK 701,000
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns WELLE ENTREPRENØR AS?

JAN-ERIK RØRVIK
WELLE ENTREPRENØR AS
NOK 1.6m rev. · NOK −226,000 profit

WELLE ENTREPRENØR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about WELLE ENTREPRENØR AS

Who owns WELLE ENTREPRENØR AS?

JAN-ERIK RØRVIK is the largest registered owner, with 50.0%.

What is the revenue of WELLE ENTREPRENØR AS?

WELLE ENTREPRENØR AS had revenue of NOK 1.6m in 2024.

Where is WELLE ENTREPRENØR AS based?

WELLE ENTREPRENØR AS has its business address in Øyer.

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.