BIZTRAC BETA
Graphic design and visual communication activities

LATOR SKILT AS

Org. no. 930789399 Limited company (AS) Bjørnafjorden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 12,000
Equity NOK −45,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−45k kr).

LATOR SKILT AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 930789399. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen Produksjoner og salg av skilt - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 12,000
Equity
NOK −45,000
Est. value
NOK 121,000

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-12.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LATOR SKILT AS?

SILJE ELDØY GRØNVIGH
LATOR SKILT AS
NOK 2.3m rev. · NOK 12,000 profit

LATOR SKILT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LATOR SKILT AS

Who owns LATOR SKILT AS?

SILJE ELDØY GRØNVIGH is the largest registered owner, with 50.0%.

What is the revenue of LATOR SKILT AS?

LATOR SKILT AS had revenue of NOK 2.3m in 2025.

Where is LATOR SKILT AS based?

LATOR SKILT AS has its business address in Os.

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.