biztrac. BETA
COMPANY REGISTER PROFILE
919063173 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

SPIS SUNT AS

Org. no. 919063173 Limited company (AS) Nittedal Incorporated 2017 Active
Revenue 2025 NOK 2.8m
Operating profit NOK 287,000
Equity NOK 405,000
Incorporated 2017
Employees 6
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-08-02 Adresseendring registrert 2026-08-02.

SPIS SUNT AS is registered as a limited company in Nittedal, Akershus with organisation number 919063173. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av vafler, smørbrød, pannekaker, supper, is m.m. samt drikke. Catering”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 287,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▲ +9 %
Operating profit
NOK 287,000
▲ +67 %
Equity
NOK 405,000
▲ +52 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
-0.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
-14877.5%
Not satisfactory
Return on total assets
Solidity
832.0%
Very good
Equity as a share of total capital

Who owns SPIS SUNT AS?

SPIS SUNT AS
NOK 2.8m rev. · NOK 287,000 profit

SPIS SUNT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPIS SUNT AS

Who owns SPIS SUNT AS?

Lukasz Albert Kmito is the largest registered owner, with 100.0%.

What is the revenue of SPIS SUNT AS?

SPIS SUNT AS had revenue of NOK 2.8m in 2025.

Who is the general manager of SPIS SUNT AS?

Lukasz Albert Kmito is registered as general manager of SPIS SUNT AS.

Where is SPIS SUNT AS based?

SPIS SUNT AS has its business address in Slattum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.