BIZTRAC BETA
Rental and operating of own or leased real estate

VIKING KVARTALET AS

Org. no. 914120365 Limited company (AS) Indre Østfold Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 747,000
Operating profit NOK 488,000
Equity NOK 1.0m
Incorporated 2014
Share capital NOK 1.0m

Signals

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

VIKING KVARTALET AS is registered as a limited company in Indre Østfold, Østfold with organisation number 914120365. 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 1.0m, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 747,000 in revenue and NOK 488,000 in operating profit.

Key figures · 2025

Revenue
NOK 747,000
Operating profit
NOK 488,000
Equity
NOK 1.0m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns VIKING KVARTALET AS?

SØHOEL INVEST AS
VIKING KVARTALET AS
NOK 747,000 rev. · NOK 488,000 profit

VIKING KVARTALET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKING KVARTALET AS

Who owns VIKING KVARTALET AS?

SØHOEL INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VIKING KVARTALET AS?

VIKING KVARTALET AS had revenue of NOK 747,000 in 2025.

Who is the general manager of VIKING KVARTALET AS?

Terje Søhoel is registered as general manager of VIKING KVARTALET AS.

Where is VIKING KVARTALET AS based?

VIKING KVARTALET AS has its business address in Askim.

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.