BIZTRAC BETA
Business and other management consultancy activities

BIRKELAND & SALVESEN AS

Org. no. 913778588 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 450,000
Operating profit NOK 423,000
Equity NOK 1.9m
Incorporated 2014
Share capital NOK 30,000

BIRKELAND & SALVESEN AS is registered as a limited company in Oslo, Oslo with organisation number 913778588. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, finansieringsvirksomhet, rådgivning, handel og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 450,000 in revenue and NOK 423,000 in operating profit.

Key figures · 2024

Revenue
NOK 450,000
Operating profit
NOK 423,000
Equity
NOK 1.9m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns BIRKELAND & SALVESEN AS?

TRYGVE CHRISTIAN MOE
BIRKELAND & SALVESEN AS
NOK 450,000 rev. · NOK 423,000 profit

BIRKELAND & SALVESEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BIRKELAND & SALVESEN AS own?

BIRKELAND & SALVESEN AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BIRKELAND & SALVESEN AS

Who owns BIRKELAND & SALVESEN AS?

TRYGVE CHRISTIAN MOE is the largest registered owner, with 100.0%.

What is the revenue of BIRKELAND & SALVESEN AS?

BIRKELAND & SALVESEN AS had revenue of NOK 450,000 in 2024.

Where is BIRKELAND & SALVESEN AS based?

BIRKELAND & SALVESEN 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 15.06.2026.

Report a problem

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