BIZTRAC BETA
Wholesale of beverages

NERSNÆS AS

Org. no. 985331138 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 1.1m
Equity NOK 4.4m
Incorporated 2003
Share capital NOK 100,000

NERSNÆS AS is registered as a limited company in Oslo, Oslo with organisation number 985331138. The business is classified under wholesale of beverages (NACE 46.340). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Erverv av rettigheter til import, eksport og salg av varer, i eget navn eller som agent, konsulentvirksomhet, kjøp, salg, utleie av fast eiendom og verdipapirer, samt alt som står i forbindelse med dette, herunder delta i annen virksomhet med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 1.1m
Equity
NOK 4.4m
Est. value
NOK 6.5m

Financial health · 2024

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

Who owns NERSNÆS AS?

OLA NERSNÆS
NERSNÆS AS
NOK 1.2m rev. · NOK 1.1m profit

NERSNÆS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NERSNÆS AS own?

NERSNÆS AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about NERSNÆS AS

Who owns NERSNÆS AS?

OLA NERSNÆS is the largest registered owner, with 100.0%.

What is the revenue of NERSNÆS AS?

NERSNÆS AS had revenue of NOK 1.2m in 2024.

Who is the general manager of NERSNÆS AS?

Ola Nersnæs is registered as general manager of NERSNÆS AS.

Where is NERSNÆS AS based?

NERSNÆS 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.