biztrac. BETA
COMPANY REGISTER PROFILE
936512186 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Legal activities

WIESE ADVOKATFIRMA AS

Org. no. 936512186 Limited company (AS) Oslo Incorporated 2025 Active
Revenue 2025 NOK 13,000
Operating profit NOK −15,000
Equity NOK 15,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

WIESE ADVOKATFIRMA AS is registered as a limited company in Oslo, Oslo with organisation number 936512186. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Advokatvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
Operating profit
NOK −15,000
Equity
NOK 15,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns WIESE ADVOKATFIRMA AS?

WIESE ADVOKATFIRMA AS
NOK 13,000 rev. · NOK −15,000 profit

WIESE ADVOKATFIRMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WIESE ADVOKATFIRMA AS

Who owns WIESE ADVOKATFIRMA AS?

Jo Daniel Wiese is the largest registered owner, with 100.0%.

What is the revenue of WIESE ADVOKATFIRMA AS?

WIESE ADVOKATFIRMA AS had revenue of NOK 13,000 in 2025.

Who is the general manager of WIESE ADVOKATFIRMA AS?

Jo Daniel Wiese is registered as general manager of WIESE ADVOKATFIRMA AS.

Where is WIESE ADVOKATFIRMA AS based?

WIESE ADVOKATFIRMA AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.