BIZTRAC BETA
Combined facilities support activities

ULLENSAKER VAKTMESTERTJENESTER AS

Org. no. 818746962 Limited company (AS) Ullensaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 1.4m
Equity NOK 1.1m
Incorporated 2017
Employees 7
Share capital NOK 30,000

ULLENSAKER VAKTMESTERTJENESTER AS is registered as a limited company in Ullensaker, Akershus with organisation number 818746962. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2017 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Diverse vaktmestertjenester som snørydding, hagearbeid, maling, rydding, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 7.8m
Operating profit
NOK 1.4m
Equity
NOK 1.1m
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
1.44
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.1%
Good
Equity as a share of total capital

Who owns ULLENSAKER VAKTMESTERTJENESTER AS?

HORIA GEORGIAN MORHAN
ULLENSAKER VAKTMESTERTJENESTER AS
NOK 7.8m rev. · NOK 1.4m profit

ULLENSAKER VAKTMESTERTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ULLENSAKER VAKTMESTERTJENESTER AS

Who owns ULLENSAKER VAKTMESTERTJENESTER AS?

HORIA GEORGIAN MORHAN is the largest registered owner, with 50.0%.

What is the revenue of ULLENSAKER VAKTMESTERTJENESTER AS?

ULLENSAKER VAKTMESTERTJENESTER AS had revenue of NOK 7.8m in 2025.

Where is ULLENSAKER VAKTMESTERTJENESTER AS based?

ULLENSAKER VAKTMESTERTJENESTER AS has its business address in Nordkisa.

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.