BIZTRAC BETA
COMPANY REGISTER PROFILE
928663221 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ADVOKAT HÅVARD FLATLAND

Org. no. 928663221 Sole proprietorship (ENK) Vestby Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 2.0m
Equity NOK 1.2m

Signals

1 flags
  • Nylig endring 2026-08-05 Adresseendring registrert 2026-08-05.

ADVOKAT HÅVARD FLATLAND is registered as a sole proprietorship in Vestby, Akershus with organisation number 928663221. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 2.0m
Equity
NOK 1.2m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns ADVOKAT HÅVARD FLATLAND?

No shareholders are registered for ADVOKAT HÅVARD FLATLAND in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT HÅVARD FLATLAND

What is the revenue of ADVOKAT HÅVARD FLATLAND?

ADVOKAT HÅVARD FLATLAND had revenue of NOK 3.2m in 2025.

Where is ADVOKAT HÅVARD FLATLAND based?

ADVOKAT HÅVARD FLATLAND has its business address in Vestby.

Property

Business address Vestbyveien 21, 1543 Vestby
Cadastral unit 3216-8/133/0/0
Building Kontor- og administrasjonsbygning, rådhus · 2 units

13 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.