BIZTRAC BETA
Rental and operating of own or leased real estate

MOSBY BENSIN EIENDOM AS

Org. no. 988239461 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.7m
Equity NOK 3.6m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MOSBY BENSIN EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 988239461. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i og utleie av fast eiendom til salg og utleie samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 1.7m
Equity
NOK 3.6m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns MOSBY BENSIN EIENDOM AS?

HAG INVEST AS
MOSBY BENSIN EIENDOM AS
NOK 2.1m rev. · NOK 1.7m profit

MOSBY BENSIN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MOSBY BENSIN EIENDOM AS

Who owns MOSBY BENSIN EIENDOM AS?

HAG INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of MOSBY BENSIN EIENDOM AS?

MOSBY BENSIN EIENDOM AS had revenue of NOK 2.1m in 2025.

Where is MOSBY BENSIN EIENDOM AS based?

MOSBY BENSIN EIENDOM AS has its business address in Kristiansand S.

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.