BIZTRAC BETA
Legal activities

ADVOKAT STIG E. MORTENSEN AS

Org. no. 811880612 Limited company (AS) Vågan Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 592,000
Equity NOK 1.6m
Incorporated 2013
Share capital NOK 100,000

ADVOKAT STIG E. MORTENSEN AS is registered as a limited company in Vågan, Nordland with organisation number 811880612. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Advokatvirksomhet og annet som står i naturlig sammenheng med dette, samt investeringer i verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 592,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 592,000
Equity
NOK 1.6m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns ADVOKAT STIG E. MORTENSEN AS?

STIG ERIK MORTENSEN
ADVOKAT STIG E. MORTENSEN AS
NOK 4.1m rev. · NOK 592,000 profit

ADVOKAT STIG E. MORTENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKAT STIG E. MORTENSEN AS

Who owns ADVOKAT STIG E. MORTENSEN AS?

STIG ERIK MORTENSEN is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT STIG E. MORTENSEN AS?

ADVOKAT STIG E. MORTENSEN AS had revenue of NOK 4.1m in 2025.

Who is the general manager of ADVOKAT STIG E. MORTENSEN AS?

Stig Erik Mortensen is registered as general manager of ADVOKAT STIG E. MORTENSEN AS.

Where is ADVOKAT STIG E. MORTENSEN AS based?

ADVOKAT STIG E. MORTENSEN AS has its business address in Svolvær.

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.