BIZTRAC BETA
COMPANY REGISTER PROFILE
993946125 ORG. NO. 2023 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Legal activities

STÅLE LANDMARK RÅDGIVINGSTJENESTER

Org. no. 993946125 Sole proprietorship (ENK) Larvik Active
Ownership graph ↗
Revenue 2023 NOK 356,000
Operating profit NOK 35,000
Equity NOK 109,000

STÅLE LANDMARK RÅDGIVINGSTJENESTER is registered as a sole proprietorship in Larvik, Vestfold with organisation number 993946125. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2023 financial year, show NOK 356,000 in revenue and NOK 35,000 in operating profit.

Former names: ADVOKAT STÅLE LANDMARK

Key figures · 2023

Revenue
NOK 356,000
Operating profit
NOK 35,000
Equity
NOK 109,000
Est. value
NOK 221,000

Financial health · 2023

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

Who owns STÅLE LANDMARK RÅDGIVINGSTJENESTER?

No shareholders are registered for STÅLE LANDMARK RÅDGIVINGSTJENESTER in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STÅLE LANDMARK RÅDGIVINGSTJENESTER

What is the revenue of STÅLE LANDMARK RÅDGIVINGSTJENESTER?

STÅLE LANDMARK RÅDGIVINGSTJENESTER had revenue of NOK 356,000 in 2023.

Where is STÅLE LANDMARK RÅDGIVINGSTJENESTER based?

STÅLE LANDMARK RÅDGIVINGSTJENESTER has its business address in Larvik.

Property

Business address Rødbergkollen 4, 3267 Larvik
Cadastral unit 3909-4050/56/0/0
Building Enebolig · 1 unit

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.