BIZTRAC BETA
Accounting and bookkeeping

WIESE ØKONOMI AS

Org. no. 911936615 Limited company (AS) Luster Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 779,000
Operating profit NOK 44,000
Equity NOK 31,000
Incorporated 2013
Share capital NOK 48,000

WIESE ØKONOMI AS is registered as a limited company in Luster, Vestland with organisation number 911936615. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2013. Registered share capital is NOK 48,000, divided into 30 shares. The company's stated purpose is: “Regnskapsføring for andre og økonomisk rådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 779,000 in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 779,000
Operating profit
NOK 44,000
Equity
NOK 31,000
Est. value
NOK 229,000

Financial health · 2024

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.2%
Weak
Equity as a share of total capital

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

Who owns WIESE ØKONOMI AS?

LENE WAAGSBØ WIESE
WIESE ØKONOMI AS
NOK 779,000 rev. · NOK 44,000 profit

WIESE ØKONOMI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WIESE ØKONOMI AS own?

WIESE ØKONOMI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WIESE ØKONOMI AS

Who owns WIESE ØKONOMI AS?

LENE WAAGSBØ WIESE is the largest registered owner, with 100.0%.

What is the revenue of WIESE ØKONOMI AS?

WIESE ØKONOMI AS had revenue of NOK 779,000 in 2024.

Who is the general manager of WIESE ØKONOMI AS?

Lene Waagsbø Wiese is registered as general manager of WIESE ØKONOMI AS.

Where is WIESE ØKONOMI AS based?

WIESE ØKONOMI AS has its business address in Skjolden.

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.