BIZTRAC BETA
Public relations and communication activities

BRØDRENE ALNES AS

Org. no. 830801952 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 287,000
Operating profit NOK 79,000
Equity NOK 127,000
Incorporated 2023
Share capital NOK 30,000

BRØDRENE ALNES AS is registered as a limited company in Oslo, Oslo with organisation number 830801952. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen kommunikasjon og markedsføring - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 287,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2025

Revenue
NOK 287,000
Operating profit
NOK 79,000
Equity
NOK 127,000
Est. value
NOK 360,000

Financial health · 2025

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

Who owns BRØDRENE ALNES AS?

ALEKSANDER GODØ ALNES
BRØDRENE ALNES AS
NOK 287,000 rev. · NOK 79,000 profit

BRØDRENE ALNES AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØDRENE ALNES AS

Who owns BRØDRENE ALNES AS?

ALEKSANDER GODØ ALNES is the largest registered owner, with 33.3%.

What is the revenue of BRØDRENE ALNES AS?

BRØDRENE ALNES AS had revenue of NOK 287,000 in 2025.

Who is the general manager of BRØDRENE ALNES AS?

Aleksander Godø Alnes is registered as general manager of BRØDRENE ALNES AS.

Where is BRØDRENE ALNES AS based?

BRØDRENE ALNES 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.