BIZTRAC BETA
COMPANY REGISTER PROFILE
954682684 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Freight ocean transport

ANS STAVODD

Org. no. 954682684 General partnership (ANS) Stavanger Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 77,000
Operating profit NOK 52,000
Equity NOK 1.1m
Incorporated 1982

ANS STAVODD is registered as a general partnership in Stavanger, Rogaland with organisation number 954682684. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1982. The company's stated purpose is: “Handel, eie og utleie av faste eiendommer samt delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 77,000 in revenue and NOK 52,000 in operating profit.

Key figures · 2025

Revenue
NOK 77,000
Operating profit
NOK 52,000
Equity
NOK 1.1m
Est. value
NOK 730,000

Financial health · 2025

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

Who owns ANS STAVODD?

No shareholders are registered for ANS STAVODD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ANS STAVODD

What is the revenue of ANS STAVODD?

ANS STAVODD had revenue of NOK 77,000 in 2025.

Where is ANS STAVODD based?

ANS STAVODD has its business address in Stavanger.

Property

Business address Paradisveien 28, 4012 Stavanger
Cadastral unit 1103-55/997/0/0
Building Enebolig · 1 unit

9 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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