BIZTRAC BETA
Rental and operating of own or leased real estate

DITT LAGER AS

Org. no. 913386175 Limited company (AS) Sandnes Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −5,000
Equity NOK 434,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

DITT LAGER AS is registered as a limited company in Sandnes, Rogaland with organisation number 913386175. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drifting av lagerhotell, utleie av minilager hovedsakelig til privatpersoner, samt hva hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −5,000
Equity
NOK 434,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns DITT LAGER AS?

RAGNAR OFTEDAL
DITT LAGER AS
NOK 1.4m rev. · NOK −5,000 profit

DITT LAGER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DITT LAGER AS

Who owns DITT LAGER AS?

RAGNAR OFTEDAL is the largest registered owner, with 50.0%.

What is the revenue of DITT LAGER AS?

DITT LAGER AS had revenue of NOK 1.4m in 2025.

Who is the general manager of DITT LAGER AS?

Ragnar Oftedal is registered as general manager of DITT LAGER AS.

Where is DITT LAGER AS based?

DITT LAGER AS has its business address in Sandnes.

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.