BIZTRAC BETA
COMPANY REGISTER PROFILE
922028060 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LUND TOMTESELSKAP AS

Org. no. 922028060 Limited company (AS) Lund Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 853,000
Incorporated 2018
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

LUND TOMTESELSKAP AS is registered as a limited company in Lund, Rogaland with organisation number 922028060. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Erverve, videreutvikle og selge næringsarealer, samt alt som hører naturlig til dette”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 853,000
Est. value
NOK 778,000

Financial health · 2025

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

Who owns LUND TOMTESELSKAP AS?

LUND TOMTESELSKAP AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUND TOMTESELSKAP AS

Who owns LUND TOMTESELSKAP AS?

JOHS RASMUSSEN AS is the largest registered owner, with 30.0%.

Where is LUND TOMTESELSKAP AS based?

LUND TOMTESELSKAP AS has its business address in Moi.

Property

Business address Stasjonsveien 46, 4460 Moi
Cadastral unit 1112-24/110/0/0

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.